Why I No Longer Use MVC Frameworks
People have a hard time with MVC because frameworks that use the phrase MVC are always more complex than necessary.<p>There&#x27;s a simple set of separations that you need to pay attention to for your code to be what I like to call &quot;not stupid&quot;.<p>1.  Separate your code from your data.  You shouldn&#x27;t be kicking out HTML with your code, like this guy does in figure 1.  When you combine HTML or any display information with code that means your designer is your coder and your coder is your designer.  Designers suck at code.  Coders suck at design.  Keep that shit separate.<p>2. Separate your logic code from your code that changes your data.  You shouldn&#x27;t be running updates&#x2F;saves&#x2F;inserts from 30 different locations in your code.  Define your interface, expect that interface to work.  When you need to shift from Oracle to Redis to RDS, you shouldn&#x27;t have to refactor 80% of your application.  You refactor your data update code and leave everything else that works alone.<p>There you have it.  Model, View, Controller.  You have a data model that can be displayed in any number of ways, and you control CRUD on that Model via the controller.  It&#x27;s not a religion.  Just make sure there&#x27;s a logical separation within your code so you can delegate as your team and application grows.<p>Architect things logically and call it whatever you want.