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
Some thoughts on my experience using the latest Gen-AI tools| Spaghetti and Hammers
For the past ~3 years, I have been making a living as a community professional. I help startups turn their faceless audiences into online communities where they can show their personalities and create value for each other. I love it! But in my earlier life, before I was into communities,| Chronicles of Nityesh
The Asset PipelineThis guide explains how to handle essential asset management tasks.After reading this guide, you will know: What is an asset pipeline. The main features of Propshaft, and how to set it up. How to migrate from Sprockets to Propshaft. How to use other libraries for more advanced asset management.| Ruby on Rails Guides
We pay attention to the minutia in pull request reviews, and for good reasons.| 37signals Dev
The proposal for a talk I gave at RailsConf 2019.| Kevin Murphy
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
Rails concerns have received much criticism over the years. Are they the solution to all the problems or something to avoid at all costs? I think a problem with concerns is that you can use them however you want, so no surprise you can shoot yourself in the foot when doing it. After all, concerns are just Ruby mixins with some syntax s...| world.hey.com