Problems with PHP itself aside, rolling your own from scratch only ever works out well for projects that start small and stay small. Even if the code is sane and readable, a developer starting with a site like this will need to understand either all of the patterns that are being used or to read and understand all of the code before being able to confidently and effectively work with it.
Contrast this to a framework, where similarly-sane code will yield something anyone with experience in the framework can almost-immediately begin working with.
Both have an up-front cost; however, the first incurs that cost every time any new developer starts working with any project done in such a way. The second is incurred once, period, making the startup time on any project on the same framework dramatically lower.
Frameworks are by no means a silver bullet, but their utility should not be underestimated, and the very nasty maintenance cost effects of the parent's post should be similarly understood.
But you can come up with a clear architecture without using a framework. For example, most projects I work on are well suited for a modular design. I can build them from many small, independent parts. So I write lots of PHP scripts consisting of some SQL queries on top and some presentation logic below. Introducing an ORM and separating Model/View/Controller would just add unnecessary complexity!
In my case, modularity ensures maintainability; there's no need for anyone to read all of the code before they can start working on something. Reading all of the code is only necessary if you write spaghetti code; but inexperienced developers will have no problem writing unmaintainable spaghetti code using any choice of framework!
When I leave the project, any PHP developer will be able to pick up and implement changes within hours.
Famous last words for PHP apps rolled from scratch with no unit tests.
Without tests I have less confidence with modifying another persons code. Without a framework it can be difficult to figure out the structure unless there is good documentation or the project has been well designed and structured (almost never the case).
Also I tend to either find problems with SQL injection,XSS or CSRF because they don't have a framework to help solve these or they have implemented their own solutions which are inevitably buggy or weird in some way.
That said, they don't allow SQL injections because they don't have a framework, they did it because they're stupid. Using a framework (and following the docs) will help save us from their stupidty, but so would learning about security issues.
Frameworks are largely about speed. They should make you develop quicker because loads of code is pre-written and generally it is of a higher quality than what you'll knock out in a few days because hundreds of man hours go into those libs.
Once you learn a singular framework, it cuts out any additional effort you need to go through to create said prototypes and you end up with a prototype that can be extended to production standard.
Sure you need to spend the time to learn it, but that's a one time deal for the most part.
Yii's CRUD code gen is incredibly nice to work with off the bat, so it really comes down to customizing json form validation messages and packing some partials views in with the response.
edit: It has ended up being that a good 70% of my time in web app dev is devoted to the tedium of changing little UI crap (Can this blue pop a little more? Can you put some shadowing here? I like this slider but I'm not feeling hyped about it... repeat ad infinitum), and not so much with complex backend work. It takes about two days, as you said, to get the server code going strong, and then two weeks to move divs around by an em here or there.
Congratulations. But will they be able to make changes without breaking what you did? That's the mark of a good developer. Anyone can make something, but it takes real experience and constant thought about how your code will be observed by others down the line to make a truly great product.
> Problems with PHP itself aside, rolling your own from scratch only ever works out well for projects that start small and stay small.
Small projects were what PHP was initially designed for. By the way the OP is talking, I believe that he's working on mostly brochureware or at least small/simple apps that don't require 24/7 monitoring or maintenance.
Avoiding frameworks, unit tests and client-side JavaScript is probably not as helpful. True, they can add bloat and complexity if you don't learn how to work with them.
Check out a framework like Laravel. Once you get over the hump you won't want to look back. I have my own framework called Phreeze which of course I'm partial towards but there are more recognized ones out there.
The advantage is that I can create a working prototype in days. I can show something to the client very early, and I don't spend months to fulfill specifications the client didn't really understand in the first place.
When I leave the project, any PHP developer will be able to pick up and implement changes within hours. My code isn't elegant in any way, but it's simple.