Over the fall, we tried out Ansible for some of our latest machine provisioning needs and we liked our experience with it. We had been using Opscode Chef up until recently but a lot of the team members were getting stuck climbing its steep learning curve. We had also given Juju a spin but the cycle of making changes and testing them was simply too slow and painful to continue using it.
We recently moved all our code repositories from Atlassian’s hosted SVN to BitBucket and took the opportunity to revisit our deployment process. We had been operating using SVN trunk for ongoing development and stabilizing it whenever we wanted to cut releases. This approach worked well in the early days but started to show its’ challenges as we added developers to the team and worked on parallel tracks. So the move to Git presented the perfect time to consider a development process that would be a better fit for a DVCS. Enter Git-Flow.
I am embarrassed to admit but I stayed with Yahoo! Wordpress Hosting way too long. Maybe it was inertia, maybe it was because I hadn’t paid attention to my site in a long time. Whatever the reason was, my recent renewed commitment to revitalizing my blog required that I take another look at my hosting situation.
Did you happen to catch all the commotion on Hacker News? Blanket statements like "when it comes to hiring, I'll take a Github commit log over a resume any day" tend to fire people up (probably why the poster chose that wording anyway). Don't get sucked in.