blogpro.toutantic.net
Archives | Aurélien Pelletier
http://blogpro.toutantic.net/archives
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). April 2004 ( View complete archive page. Flex, WebWork, Struts et Spring en 1 jour. May 2004 ( View complete archive page. SOA et Web Services. August 2004 ( View complete archive page. September 2004 ( View complete archive page. Strus and JSF future from the source. Software is too expensive to build cheaply. October 2004 ( View complete archive page. Open source Open What? A use case for AOP.
blogpro.toutantic.net
Codex | Aurélien Pelletier
http://blogpro.toutantic.net/codex
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). L’art du développement logiciel est en perpétuelle évolution, c’est un attrait pour les geeks mais une difficulté pour tous. Nous sommes d’ éternels débutants. Condamnés à consulter jour après jour les nouveaux blogs, présentation et autres tutoriaux pour rester opérationnel. Les Technologies de l’Information et de la Communication (TIC). Leave a Reply Cancel reply. Required fields are marked *.
blogpro.toutantic.net
docker | Aurélien Pelletier
http://blogpro.toutantic.net/tag/docker
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). My schedule for Google I/O 2014. This year Google I/O will be about DDD, have you read the blue book. We can expect a lot of announcements and sessions around Android. And a lot more, as you can see in the list of sessions I’m planning to attend. Can’t wait to learn more about Docker, Polymer, DevOps and the Google cloud platform! Day one June 25. Announcements, goodies,…. And stay focused again!
blogpro.toutantic.net
My schedule for Google I/O 2014 | Aurélien Pelletier
http://blogpro.toutantic.net/2014/06/24/google-io-2014-schedule
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). My schedule for Google I/O 2014. This year Google I/O will be about DDD, have you read the blue book. We can expect a lot of announcements and sessions around Android. And a lot more, as you can see in the list of sessions I’m planning to attend. Can’t wait to learn more about Docker, Polymer, DevOps and the Google cloud platform! Day one June 25. Announcements, goodies,…. And stay focused again!
blogpro.toutantic.net
Another Git branching model | Aurélien Pelletier
http://blogpro.toutantic.net/2012/01/02/another-git-branching-model
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). Another Git branching model. We’ve switched to git at work a few month ago. Not an easy task but the rewards are worth the trouble. Our branching model was based on Git Flow. Because it’s well documented and gives you a structure to start with DVCS. Well, after a few iterations it wasn’t working as expected in our context. So we had to come up with our own workflow. We have three branches with an i...
blogpro.toutantic.net
Google Cloud Platform technical qualification training : Cloud SQL | Aurélien Pelletier
http://blogpro.toutantic.net/2014/10/28/google-cloud-platform-technical-qualification-training-cloud-sql
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). Google Cloud Platform technical qualification training : Cloud SQL. Not much to say about Cloud SQL, it is simply a fully managed mysql database version 5.5 and 5.6. Fast connection to App and Compute Engine but accessible from anywhere. (you have to enable the access). Google can manage replication for you. mysql instance are brought up on demand and can go away after 4 hours of inactivity.
blogpro.toutantic.net
gestion de projet | Aurélien Pelletier
http://blogpro.toutantic.net/tag/gestion-de-projet
Web,Open source, Agile, Architecture, Java. Les Technologies de l’Information et de la Communication (TIC). Tag Archives: gestion de projet. Another Git branching model. We’ve switched to git at work a few month ago. Not an easy task but the rewards are worth the trouble. Our branching model was based on Git Flow. I guess Git Flow works well on a clean code base with good test coverage. But on legacy code, where one feature means two regressions, a release branch is like the vietnam war. We have three br...