A Review of MVC
mikepackdev.com
mikepackdev.com
Nice snippet of advice there. Also the rest of Trygve's original post is an excellent reminder (and in simple terms) of MVC as an idea, rather than MVC as a label to slap on the next bit of JS code you publish on github ... which is basically all the intro paragraph says.
I do believe that many nouvelle programmers in their rush to absorb and contribute to the art integrate too many things too quickly and try to fabricate the magic recipe they just learned about into a hammer they can pound on everything regardless of whether the particular problem is a nail or not.
I'm a strong advocate for using no framework, then building your own, then and only then introducing a library or framework because they can do it better.
This allows you to understand the pain of its absence, understand how to fundamentally solve the problem through abstraction or organization, and then fully leverage and reap the benefits of a well designed framework.
Some would say you don't need to walk 100 miles to understand the value of a car. But thats from the product side. I would say you need to understand the weaknesses of a car to build the next generation vehicle.
Including Thing: http://heim.ifi.uio.no/~trygver/1979/mvc-1/1979-05-MVC.pdf
Revision: http://heim.ifi.uio.no/~trygver/1979/mvc-2/1979-12-MVC.pdf