'Ruby on Rails hurts developer productivity'

I tried to warn him, but he wouldn’t listen. Jakob Skjerning, who helped redesign rubyonrails.com and whom I worked with on Daily Rush, has been sucked into the Rails vortex:

After having gotten used to RoR for a private project or 2, all the web development stuff I do at work feels ugly, clunky and unproductive, simply because I am not using Ruby on Rails for it.

So take my advice: If you are stuck doing legacy work on a legacy system, don’t think about learning RoR – you might never want to go back to work if you do.

So let that be a warning to all of the prospect Rails programmers out there. Be careful what you get started with.

We actually have a thread on feeling dirty about not doing Rails on the mailing list right now. Rick Olson writes:

Going back to ASP.Net development makes me feel dirty. What? I have
to update the stored procedure, the model, the DAL, the form, and
create a new server control just to add a property???
blog comments powered by Disqus