Post

I’ve been doing DevOps and infrastructure for over 17 years and have worked extensively with Rails. My main focus has been deployment, performance monitoring, multi-environment support, and ensuring things run optimally, even at scale.

One side of my brain (“The Optimizer”) thrives on imperfections, relentlessly improving things. I love that part, and I’m pretty successful at it (you be the judge). But it comes with a downside.

The other side (“The Creator”) has always had plenty of random ideas, but executing them has always been difficult for me: choosing THE BEST tech, worrying about scalability, and doubting each decision afterward—all of this drained The Creator’s energy.

This conflict was especially noticeable when I tried Next.js: “How should I run background jobs?”, “What if I don’t use Vercel?”, “Is my module structure optimal?” Endless overthinking, courtesy of The Optimizer.

Recently, I started using Rails to quickly test out a simple product idea. Surprisingly, I’ve avoided getting caught in optimization loops.

Whatever @DHH did, he knew exactly what he was doing with the Rails philosophy: convention-over-configuration and “batteries included.” It seems purpose-built to quiet my perfectionist brain: I just use what’s provided unless there’s a compelling reason to change.

My ideas might not always be groundbreaking or in high demand, but Rails provides a reliable platform to experiment, quickly iterate, and actually ship something tangible. Once it's built, the exciting next challenge is clear: learning how to market it effectively.