the Twitter Blog has something posted that I thought was a nice in site.

“For stressed engineers, it’s tempting to think that another solution - anything but what you’re using now! - will solve all your problems. Maybe you start dreaming up the perfect framework on a whiteboard, or maybe you start scouring the web for the fastest, newest, most experimental technology. In the long run, picking a foundation you’re comfortable with and making sensible iterations towards your performance goals will yield a bigger win. You have to be careful while iterating: watch your database, test thoroughly, and be ready to roll back when things break (and they will).”

ColdFusion has suffered from this. Since it’s ease of use invites users to create applications that may not be the best methodologies means that sometimes legacy apps can be crap. I look at some of the stuff I wrote 8 years ago and Good Lord it makes me cringe.

Though they are talking about Ruby and the Rails framework I think that it applies to just about any language. They all have their strengths and weaknesses and in the end will probably serve about 90% of all your needs with the other 10% just being a rethink of the way you do things.

 I think that if more people concentrated on making their apps better then complaining and wanting to move to the “New Kid On the Block” that their programming life would be a LOT less stressful.