I dug a bit into the #FIZZY code and I’m surprised. They use basically a vanilla Rails gem set without any of the libraries considered "standard" these days like Devise, ViewComponent, Phlex, RSpec, etc... Nothing fancy, zero bloat. I thought I was a purist at Tribely, but @37signals takes it to a whole new level. I bet that was @dhh's intention all along. Mad respect for this approach. Great job and amazing study material 👍

Deploying a change with Kamal using the new local registry against my homelab server is now down to 7 seconds. Getting close to those FTP-drag-to-production days 😄🤘

At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service templates, the whole shebang. The whole senior engineering leadership came from Amazon, where they were used to each team owning a distinct service. They tried to apply that model directly. But our issues were with code ownership and poor domain modeling. The entire application could have run on just a handful of EC2 instances. What was the result? Five years later, 70% of the application is still running on the Ruby on Rails monolith. Never completed the migration. But now they have to maintain two systems. None of the original leadership works there anymore.