Rake's File Tasks allow us to define steps to create a file and to add the File Task as a prerequisite. This can be useful when deploying an application that depends on configuration files not checked in to the repo.
In the Ruby world, Capistrano has been the de-facto standard for deploying applications since it’s release in 2006. This summer however, it’s time to get excited about deployment again - version three is on the edge of a beta release and this feels like the perfect time to share some of the features about which I’m most excited.
Everyone knows retro fitting tests is not the best way to go, but you can't escape the fact that sometimes it's unavoidable. Writing integration tests after the fact can sometimes be tricky, especially when dealing with complex xpaths or trying to assert against deeply buried elements. So if you're as tired of digging around in web inspector as I am, try this instead
Moving from TextMate to Vim is probably the most significant change I’ve made to my daily development over the last year - and I’m amazed by how much difference it’s made. A few weeks back though a blog post convinced me to go one step further - I took a deep breath and deleted my entire vim install.
As Google Translate API v2 has now launched, I looked around for a gem we could quickly plug in and was surprised to find only the google-api-ruby-client - which for our needs seemed to come with a lot of dead weight. Given we only require a very limited feature set, I decided to build a tiny gem to meet just that need.