Packt: What would you say is the biggest challenge that Rails developers face today?
Chris Oliver:I would say that most of what I see people struggling with is they always want to use the hot new tools—whatever's the latest thing.
Unlock access to the largest independent learning library in Tech for FREE!
Get unlimited access to 7500+ expert-authored eBooks and video courses covering every tech area you can think of.
Renews at $19.99/month. Cancel anytime
But I don’t see enough developers, not just Rails devs, just… go build stuff. Go get good at understanding how users use it. Learn how to fix what feels clunky. Learn to build things that are accessible.
The biggest challenge today is the sheer complexity. You need to know keyboard accessibility, CSS, JavaScript, server-side performance, database indexing, good architecture—it’s an overwhelming amount just to build solid software.
A lot of devs are chasing magical libraries that promise to just “do it all,” but it almost never works perfectly. There are always weird edges that don’t quite fit.
The real skill is knowing when to say:
“We can build this the way it was asked—but we could do 90% of it faster if we adjust a bit. Let’s ship that, test it, and iterate.”
At the end of the day, you’ve got to get something into your users’ hands. That’s what really matters. It’s easy to lose sight of that with so many tools and choices around.