Re:Rails 5.2
by slimed on Tuesday November 28, 2017 @08:43AM
(#15797142)
Put another way: If you're always outsourcing work like upgrading Rails versions so that your devs can focus on "features" they will never learn which design decisions they are making are extremely costly in the long run. Like, hmm, maybe I shouldn't include 4 gems just to build and test my JavaScript. Or, hmm, maybe I shouldn't write this code in a way that leaks ORM details. Testing culture is great. But it is not an antidote for kicking-the-can-down-the-road culture.
[ Parent
| on HN ]
That I can agree with. I've been using rails since version 0.9, and my predisposition is to use as few gems as possible.
Managed properly, rails and ecosystem churn is manageable. Managed poorly, it becomes reasonable to bring in an expert to repair your neglect.
But it's definitely true that rails culture doesn't make itself easy to manage.