Good Frameworks like .NET, .NET MVC, and Ruby on Rails exist for a reason. So stop writing yours. Now.

In the 10 or so years I have been a programmer I have run into a lot of “frameworks” in which to build an application. I’m relatively certain I even tried to write my own at one point or another. And, lets just be honest here, they suck. 

Here’s why:

Programmer Jack decides he’s going to write the Awesome Sweet Cool App 2.0. He’s making a 2.0 because the stupid, awful programmer before him (because you know the guy before you always sucks) wrote this thing. It’s a pain in the ass to maintain, it’s was written using AwesomeLanguage 2.4 and AwesomeLanguage 4.6.91 b1459 is out now. Either way, it’s a “complete train wreck” and Jack needs something scalable, future-proof, and maintainable. Jack toils endlessly writing a custom page handler, image handler, a form processor that will take his XML/XSL templates and convert them to XHTML forms and on submission they are sent to a custom form processor which uses a factory pattern to choose the right object to return that handles the form automatically.  All of the controls are automatically wired together so that the buttons bind to common events at runtime, and the application “just works”. FRICKIN’ AWESOME! Jack is a superstar, he beats the bad guys, he rescues the princess, and walks off into the sunset. 

More...