4 ms·
I don't think it's about performance. It's about the glut of inexperienced, underskilled Ruby devs landing seemingly simple gigs where they patch together unmai
by tdumitrescu 12y ago
I don't think it's about performance. It's about the glut of inexperienced, underskilled Ruby devs landing seemingly simple gigs where they patch together unmaintainable Rails spaghetti - ultimately saddling clients/employers with a heap of technical debt and hobbling future devs who come to these projects.
- sanderjd 12y agoThis is a case of getting what you're willing to pay for. Great work is expensive because it takes a lot of experience to do, and there are a lot of opportunities for those with a lot of experience. But if you're willing to sacrifice the "great work" part, there are plenty of people out there with less experience doing (potentially) less great work for less cost. Everybody would like above market work for below market cost, but it doesn't tend to work that way.
- jalfresi 12y agoI see what you're getting at but when Ruby/Rails was all new and shiny a couple of years back I knew an awful lot os junior/inexperienced devs who quite permanent jobs to go freelance/consulting for ruby/rails jobs because the money being paid was way above that for other similar level devs. It was pure hype, and to be fair to everyone who did this, the saw the writing on the wall and rode the wave. I even knew one SEO Exec who switched to ruby/rails contract dev work; if that isn't a warning sign, I don't know what is! Just to note, I'm a PHP dev who works in SEO, and have done for years, during the great SEO boom, so I know bad code and I know snake oil salesmen. But I think in about 12/18 months time, once all the charlatans have moved on, the ruby/rails devs left will be experienced, battle hardend legacy devs, and the respect will begin., much like the SEO industry now.