"Imagine a company that has 1000 engineers, and they share the same tech stack. Over time, a team finds the shared tech stack unsatisfactory, either because they have to write boilerplate code over and over, or the performance is not good enough, or whatever. So they decided to create their own framework on top of the shared stack. You know it's a framework and not just a library, when you hear engineers present the work using concepts & terminologies they invented,"
"This framework is well-designed and maintained by a dedicated team. We're generally happy with it, though it has some itchy points (not pain points). Being a strong and ambitious engineer, my manager proposed that we add an abstraction layer on top of it, with the aim to lower the barrier for org adoption, and solve those itchy points on the way. I was skeptical and tried convincing my manager not to do it, but failed."
Mini-frameworks form when small teams build custom frameworks on top of an organization-wide tech stack to reduce boilerplate, improve performance, or match internal mental models. These frameworks introduce new concepts and terminologies that differ from the original stack, and their creators promote them as broadly solving problems. In large companies this pattern recurs and spreads beyond its originating team. One team using a well-designed internal distributed framework considered adding another abstraction layer to ease adoption and address minor annoyances; skepticism arose but the abstraction was pursued, illustrating the cycle of mini-framework creation and adoption.
Read at Laike9m
Unable to calculate read time
Collection
[
|
...
]