3 ms·
The author makes it sound like Rails is the recommended way to build software that is maintained by a revolving door of junior developers whom you don't have to
by pavlov 6y ago
The author makes it sound like Rails is the recommended way to build software that is maintained by a revolving door of junior developers whom you don't have to motivate or compensate, because you can just hire another cog-in-the-machine when the old ones inevitably wise up to your game.
Not sure if that was the intended message.
- gremlinsinc 6y agoyeah, kind of read it that way, or as an ad for their rails churn 'shop'. More than anything seems like an ad for rails developers, nothing else. as a fullstack guy who's worked w/ rails, laravel, etc... and who's done my share of frontend stuff, I'd say focusing on the frontend might be a bigger sell, cause that shit is VERY opinionated lately. Vue vs React vs Vanilla vs Alpinejs. Do you use bootstrap or tailwinds? Backend code is rudimentary but nailing the ui stuff and also cross platform if needing mobile or w/e is much harder personally.
- biztos 6y agoAlso, it might not even work! What happens when one of your fungible junior engineers happens to be smart enough to do some tricky things even with Rails? And then she gets hired by Netflix to do something more career-enhancing than copy-pasting Ruby code from StackOverflow. Now you're stuck with your revolving door of undercompensated junior developers and a complicated Rails application. Uh-oh!
- neomindryan 6y agoThanks for this perspective. I believe it takes developers at all levels to maintain a piece of software. A developer of 10 years experience may not get professional fulfillment out of form validation changes, but a bootcamp grad shouldn't run the SOC2 audit.
- sushid 6y agoI'm pretty sure that's the intended message and the thread is simply hijacking the thesis to talk about developer compensation as usual.