[sebastian_e]

From the article:

    "I've written a lot of crappy code, and most of it is due to following Rails 'best practices.'"

Funny how the author purposes to be following 'best practices' yet is doing things such as writing 200-line methods full of if statements, putting logic in views, etc. It seems the authors woes stem directly from a lack of 'best practice' knowledge, not only of Rails but also of Ruby itself.

There will never be a framework that can completely stop developers from shooting themselves in the foot. Education is the key.

(I'll admit this comment could be much more helpful in as much as stating what the best practices are which would solve or prevent these problems but I would be repeating ground covered by better teachers than I. The truth is out there, seek and ye shall find, etc, etc!)