In the Software Development World, we are constantly bombarded with new and improved 'frameworks' that are supposed to help us write better code,  faster and cheaper.

Every framework is better than the one before.

Every framework falls short.

The main problem is that the framework's designers rarely have the end-user in mind. Not the developer mind you, but the customer that the developer is writing the software for.

Quite often after a new project is completed with the new framework, it looks alot like a project done with the old framework. The customer can't tell the difference.

Countless hours are spent learning a new framework, and every framework has its nuances, and more importantly, it's own bugs.

So a percentage of every new project is spent learning, and not doing, and as a result, the customer tends to get the same old thing again and again.

Most of the software written today is for smaller projects with smaller teams. Large software frameworks are generally overkill in these situations.

What more and more projects need is simplicity. Tone done the framework. Tone down the infrastructure. How big is the job, really? How much maintenance is required in the next year?

More and more I find that projects today are succeeding not on the framework, but on the User-Interface. Oddly enough, frameworks generally lack great User-Interface tools as they focus more on the internal code structure and database access code.

Modern Software Development has to continue to strive to meet the needs of the customer, not the developer.