Skip to content
View serradura's full-sized avatar
🎯
Focusing
🎯
Focusing

Highlights

  • Pro

Organizations

@guru-sp @guru-br @u-gems @solid-process @railswhey

Block or report serradura

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
serradura/README.md

Rodrigo Serradura

Hi, I'm Rodrigo Serradura 👋

I build Ruby and Rails tools and write about software architecture. For years I've been chasing one question:

How do you keep a codebase simple to change as it grows?

I've been building with Ruby since 2010, these days on large production Rails systems. I also founded a community for people who like arguing about this stuff.

The question has a new edge to it now. Good architecture used to be a favor you did for the next human who'd open the file. The next reader might be an AI agent instead, and it turns out the things that make code easy for a person to navigate are mostly the same things that make it cheap for an agent to reason about.

That overlap is what most of my recent work is about: Rails Whey and Solid Process (which evolved from my earlier work on μ-gems).

Rails Whey      Solid Process      u-gems      Ada.rb

🦾 Rails Whey

railswhey/app is the one I'm proudest of: the same Rails app built 28 different ways. Each branch applies a single architectural rule, from fat controller all the way to bounded contexts with separate databases, using nothing but what Rails ships with. No gems. No imported architecture.

Every branch carries its own deep-dive README: the rule it applies, before-and-after numbers (lines of code, a Rubycritic score), and a section on how the change plays for an AI coding agent. Read it front to back as one story, or jump to whichever branch matches the problem you're staring at right now.

It's a gift to the community. Explore it, learn from it, challenge it.

⚛️ Solid Process

solid-process is where the newer ideas live. It is a way to write business logic in Ruby and Rails that stays readable as the app scales. It's the evolution of u-case: same goal, fewer compatibility constraints, and everything I've learned in the years since.

💎 μ-gems

u-gems is a collection of cohesive, composable libraries with a functional heart. Each one doing a single job and stopping there.

👥 Ada.rb

I founded and run Ada.rb, the 1,000+ member community for people who care about fundamentals, architecture, design, and AI-assisted development. It is also a space where we organize meetups, bringing the community together to share knowledge and experiences.

🔗 Find me elsewhere

Pinned Loading

  1. railswhey/app railswhey/app Public

    The same Rails app, built 28 different ways — from fat controllers to bounded contexts with separate databases. No external gems. Just the framework's own tools, applied with discipline. 🦾

    74 3

  2. solid-process/solid-rails-app solid-process/solid-rails-app Public

    Twelve versions (gradually implemented) of a Web and REST API to demonstrate how Solid::Process can add value to a Ruby on Rails application.

    87 9

  3. solid-process/solid-process solid-process/solid-process Public

    Write business logic for Ruby/Rails that scales.

    Ruby 93 3

  4. u-gems/u-case u-gems/u-case Public

    Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.

    Ruby 541 31

  5. rails_app_to_refactor rails_app_to_refactor Public

    A Rails app that was intentionally designed to be refactored.

    Ruby 34 30

  6. dicas-de-programacao-em-ruby dicas-de-programacao-em-ruby Public

    Dicas para iniciantes de boas práticas de desenvolvimento de software em Ruby

    Ruby 98 2