That's what should happen over time within a domain. As you engineer the codebase it should become into its own domain framework. I feel the web industry leans heavily into only using existing frameworks and tools instead of just building it. Frameworks are actually simple, but for whatever reason the industry decided that engineering is more about gluing software together while looking at customer metrics instead of solving computer problems.
tanepiper · 4h ago
This is also what I am doing in my day job - our team own a full-stack solution for a Headless CMS and delivery platform - with that we've had to build our bits of the tech stack that over time now allow us to offer it to more team - but with that we've also had to make parts more specific to the domain we work in.
It also starts to look like a framework in parts.
tanepiper · 5h ago
One of those things - you start writing an app, and end up with a framework. I'm not planning on releasing it, but thought it might be worth sharing
It also starts to look like a framework in parts.