Question

I have a large website that I have time to convert to a nice custom-framework that I can build to my needs. I want to build my own, and not use something like Smarty because I’d like to…

1. know how all the guts of it work
2. cut any and all bloat
3. learn it, just for kicks

But, after building it in different ways, several times…I keep feeling that for the amount of “convenience” it offers, the code becomes increasingly unflexible, attempting to keep track of files becomes triple as hard (especially if you are the lone developer on the project), and there isn’t even any real awesome documentation out there.

At this point, I really need convincing…how is this going to change my life, again?

Answer 1

This has been answered already, but to put a finer point on it, I think the single attribute that encompasses when to/not MVC is scalability:

1. MVC allows clear seperation of duties (ie, front-end vs. database coders).
2. MVC is a pattern that enforces uniform coding habits.
3. Maintainability is increased as it’s easier for a new project member (who understands MVC) to grok the codebase.

If you are the sole owner of the code and don’t forsee other people joining anytime soon, then you should not need it.