Intelligent Scaffolds for Ruby on Rails

Whether you work for a large Fortune 500 company or a small start-up, chances are that most of your application engineers are embroiled in the support and maintenance of your online store.

Wednesday, November 28th, 2007

Share This:

Recently, we started working on an internal software project and decided to prototype it in Rails. I’ve messed around with Rails off and on for a year or more and I really enjoy working with it. But in a way, Rails is its own worse enemy.

Why? First, because Rails elevates your expectations for what a framework is supposed to do. Once that happens — and your eyes adjust to the dazzle of running scaffold that first time — you’re tempted to ask questions of your software infrastructure that might not normally have occurred to you.

This is exactly what happened to me as I was sketching out how many custom has_many :through code blocks we would need for the app we were writing. In it’s own way, exactly the same type of nonsense that needed to be written 10 years ago. Since I’m not a software developer by trade…

Please log in to view this content.

Not Yet a Member?