That’s a great observation. I was trying to think of how I felt about
the advice on the page:
We proffesionals are supposed to list ‘best practices’ there.
I think the ‘Set Default Values in Methods’ and the ‘Properly substitute
variables in an SQL Query’ could be considered best practices, but the
other two are best described as tips and tricks. Nothing wrong with tips
and tricks, but best practices are not quick and dirty, they are ways to
“Stay on the Rails”.
Tom, you have given me a phrase that sums up how I was feeling. Best
practices and good design patterns are created because they sum up units
of work in ways that are stable, consistent, reliable, and re-usable.
If rails work gets flooded by a bunch of “MCSE” certificate types, it
will all be tips tricks and quick fixes, with no best practices. The
Rails way is easy because we realise the value of doing things in a
Stay on the rails.
Tom M. wrote:
The bottom line is this, and it’s true for each phase of the lifecycle:
You are worth what the customer will pay. Right now, that number is a
low due to the perception that Rails is “quick and easy” where we all
that it’s actually BETTER, and will be more cost effective for the
over time due to conventions, testing, etc.
If we, the early adopters, PROVE these advantages to the customers, by
“Staying on the Rails” as I’m fond of saying, adopting the conventions,
creating unit and functional tests, etc. we’re still at the very early
stage of something that is growing explosively.
This explosion should last years, and will be very good for everyone
– Tom M.