Engineering decisions for mature Rails systems
This blog is about engineering decisions in mature Rails codebases. I write from experience—debugging production issues, simplifying systems, and choosing boring tools that survive.
I am also building RailsRevelry, a publication focused on Rails internals, debugging, and how Rails actually works under the hood.
Featured
RailsRevelry Is a Map for Understanding Rails
A short invitation to RailsRevelry, a focused publication for Rails developers who want clearer mental models of how the framework behaves.
Recent Posts
-
What SOLID Still Teaches Ruby Programmers
How SOLID changes when you read it through Ruby’s object model, duck typing, and preference for pragmatic design.
-
When a Rails Object Needs Types but Not a Table
How ActiveModel::Attributes gives tableless Rails objects type casting, defaults, and a Rails-native attribute system, and where the API still needs more support.
-
Why Your Rails Code Keeps Running After redirect_to
A small Rails debugging note about why redirect_to performs a response but does not stop Ruby control flow.
-
Ruby Beyond the Server
A collection of the various Ruby libraries and execution environments for building desktop, mobile, terminal, game, and browser applications.
-
How Rails Dispatches a Request to a Controller, and Why That Layer Matters
A shorter companion piece to the latest RailsRevelry article on the hidden dispatch layer between route matching and controller action execution.