Do you have to go to framework instead of use your own code base? Or do you have to go to mvc framework specially? Otherwise, you are out of touch of the real world, and falling way behind?
I have been using my own code base, I used "divide and conquer", I used modular programming, I separated the view from the processing pages (add/edit/delete sql etc), and even in the view pages, I separated the php processing (mostly sql and select results codes) from the html part. I offer the consistent database manipulating pages (add/edit/delete/view) for all the modules.
And the view pages html part are WYSIWYG like traditional html pages allow the art/design creative staff the max freedom. I did also offer the art design staff the CMS like oscommerce or zen cart, or Framework solution like using codeigniter, the art design staff feels that these systems are for php programmers not for the art design staff, they feel like their hands are tied up. They keep on requests I offer them this or that design freedom from these CMS or Framework. It ended up that it would be easy just develop or use my own code base instead of modify or patch the CMS or framework.
So we end up mostly using my own code base. (I am not the one who believes my own codes are better than others. As a matter of fact, I prefer to use off shelf 3rd party CMS, or use 3rd party framework and offer my patch etc. It will show more power and more expertise in the programmer's part. But due to we were design focusing company, so art designers have their say. And they end up like to use our own code base I developed.)
Like I said before, I still believe that framework vs. your own code base, mvc or not, it all depends. But when I look at the job market now, check out the job openings, I begin to think that I should use MVC framework whenever I can, no matter if it is fitting in the individual cases or not, because new employers don't care about your own code base. they only go for the popular CMS or MVC framework.
Are they right? Or they are wrong to some degrees due to they are not php developers themselves? Is the MVC framework overrated by the job market?
Frameworks have their problems before too. Popular Framework or CMS comes and goes. Slow in updates. Grow too big even grow itself to death.
With the technology grows, some sites are so advanced and require the advanced tools like these MVC frameworks. But large percentage web sites are still simple and can be handled in the simple and clean "traditional" approach. But it seems that no matter need it or not, they all go to the MVC frameworks road, is that an overkill or over engineered?
Saw a huge company with a 10 staff developing team, and spent top dollars to buy a web framework (java, xml, svn etc.), all the fancy stuff. But they even don't know how to put a simple site together. And 2 staff team with free platform php/mysql/apache can do a better job 10 times faster.
Will the old KISS principle also apply when it comes to selecting the right tool, right approach?
