2 things you must do before you build an app

I sometimes attend startup networking events in NYC. I could throw a rock and have a 50% chance of hitting someone with a web development horror story. (I wouldn't actually do it. Not again anyway :) Building a tech business is a grueling process, and developing the actual product can go wrong for a lot of reasons.

Keep reading

The database is a detail

The database is just a detail for our applications. Equally, data coming from anywhere else (Files, APIs, the Ether, etc.) is just a detail. What does that mean, exactly? We'll get to that, but first we need to discuss something else - business logic. The vast majority of Rails applications that I have worked on have had business logic in the M, the V, and the C. Why?

Keep reading

Interactors in Rails

Most Rails apps suffer from fat code. It might be fat controllers, fat models, or even fat service objects. In my view, this stems from an oversimplified view of architecture. This report will dive into one method for thinning out your controllers without moving a bunch of junk into the model.

Keep reading