I don't think there can be a professional developer out there that isn't aware of the term 'Design Patterns'. Put simply these are standard solutions to common program architecture problems that have stood the test of time and have been abstracted to the point of being applicable to a number of different domains without needing simplification first. They are often overused at the start of a project, building in flexibility for potential future requirements. One of the corner "Patterns" of Agile Development is YAGNI - You Ain't Gonna Need It. With Agile Development being "The One True Way" of developing Web Applications, are the two mutually exclusive?
After building my personal site from scratch in Symfony/PHP5 - I decided as I am leaning towards Rails now it was time to rewrite it in Rails. I had some good experiences during the process and overall I'm pleased with it. This may serve as a useful push if you're currently a PHP developer tempted by Rails.
As a contractor it is always wise to stay on top of upcoming technologies, today's niche market may be tomorrow's big earner. This year I decided to learn Ruby on Rails, so I thought I'd write a post on why I think Rails is such as excellent development system.
After a horrible experience (and putting it off for months) I've finally launched my new site. It's not feature complete but it's a good base to build on.