We love concerns and have been using them for years in large codebases. Here we share some of the design principles we use.| 37signals Dev
Maximalist positions are a thing in our industry. Take a technique, outline its drawbacks, extrapolate you can’t use it under any circumstance, and ban it forever. We are lucky that Rails embraces exactly the opposite mindset as one of its pillars.| 37signals Dev
How to create a good domain model is the subject of many books, but here’s a lesson I learned at 37signals: don’t be aseptic, double down on boldness.| 37signals Dev
A programmer who loves building things and messing with every part of the process.| 37signals Dev
Good code is a fractal: you observe the same qualities repeated at different levels of abstraction.| 37signals Dev
Active Record restates the traditional question of how to separate persistence from domain logic: what if you don’t have to?| 37signals Dev
A common critique of Rails is that it encourages a poor separation of concerns. That when things get serious, you need an alternative that brings the missing pieces. We disagree.| 37signals Dev