About bicycles and frameworks

Inspired by the topic What should be, in your opinion, a good framework?

I remember when I first started writing in PHP, I got a job at a young web desk. It had its own simple CMS, which was responsible only for handling the address (using mod_rewrite), authorization, and calling modules. Everything was fine, but it became annoying to constantly copy-paste modules. After some time, I added a simple helper there for generating forms, it became a bit more convenient and it started ...

I started writing my own CMS, at the same time studying everything related to web development, PHP and OOP. CMS is more than 3 years old; I don’t remember how many times I have completely rewritten it. Now the process continues, but begins to slowly strain. Instead of making websites and getting money for it, most of the time is spent on refining the CMS. The main idea that encourages me to write new versions is the minimum amount of code for the site. I strive to ensure that the development of the site was limited only to the imposition of templates and data description, the system should do the rest. I want to fix a lot, to make an ideal (at least for myself) system, and it seems to be working out. But after a while, again, I want to make something new, do refactoring. The modules are really compact, but the time to continually refine the system is too long. I feel that it is time to tie it up already.

In general, now I decide whether to reinvent the wheel? Maybe you should choose a framework that strictly dictates the architecture and dwell on it? Time to develop the site may increase, but it will not be tempting to change everything.