(01) — Blog
Technical writing on upgrades, performance, and the things that break in real applications.
(02) — Writing
6 posts · Newest first
The monolith gets a bad reputation it doesn't deserve. Somewhere along the way, the industry decided that a single Rails application serving an entire business was a problem to be solved rather tha...
Every new engagement starts the same way. Before any code gets written or any recommendations get made, the application gets audited. Not a cursory glance at the README — a structured evaluation of...
You've fixed the N+1 queries. You've added database indexes. You've moved email delivery to background jobs. Your app runs beautifully in development, passes CI without issue, and performs well in ...
Every slow Rails app I've profiled has the same story. The team assumes the problem is deep and architectural — maybe they need to extract microservices, maybe they need to rewrite a critical path,...
Your Rails app still works. Requests come in, responses go out, customers pay their invoices. From a business perspective, everything looks fine. So when your engineering team raises the upgrade co...
When a client comes to us with a Rails 4.2 app that's been running in production for years, the question is never "should we upgrade?" — it's "how do we upgrade without torching the business?" It's...
(03) — Start Here
Send your Rails version, rough app size, and what's prompting this. We'll tell you which tier fits and what it costs.