We know that there are many challenges involved in a Rails upgrade project. Depending on how big your application is, how old your Rails version is and how well structured your code is, it can be difficult to perform that job and keep your sanity.

It was supposed to be a very simple CLI app, 500 LOC maximum, and it was during this process that I learned first hand that the complexity of building software increases exponentially with time and added features.

Being a highly reliable commute partner to our customers, we at Cityflo take all kinds of measures to ensure high accuracy and predictability of our vehicle tracking system. Showing incorrect arrival time to our users will heavily hamper the experience that our users expect from us.

PostGIS is a fantastic, battle-tested suite of GIS extensions for Postgres. It handles most aspects of it, and is widely used, for example in OpenStreetMap’s Mapnik. But for your project, it’s most likely overkill. In a Q and A fashion, let’s discuss reasons for (not) using it.

Many Rails developers who are new to writing tests struggle with the question of what to write tests for and how. I’m about to share with you a repeatable formula that you can use to write an integration test for almost any Rails feature.