Yes, totally agreed in theory, and it sounds like y'all built a great solution for your use case. But it takes substantial effort and discipline to do something like that at scale.
At some point, you develop complex interdependencies with other systems. You need sophisticated caching for optimum build performance. Techniques like GitOps are unsustainable at a certain number of engineers/commits per hour.
What you're missing is maintenance, security, scaling, and protection from data loss.
Bespoke CI is easy to build but no one wants to be in charge of rolling out a critical security patch to that on-prem box no one's touched since that consultant from 2 years ago.
Studies have shown that later sunsets lead to worse health and economic outcomes. People who live on the western edge of a timezone earn 3% less and have higher rates of lifestyle diseases than those on the eastern edge, because they go to bed later but wake at the same socially-prescribed time, and therefore get less sleep. [1]
So why make DST instead of eliminating it entirely? It seems earlier sunset would be much more beneficial for society.
At some point, you develop complex interdependencies with other systems. You need sophisticated caching for optimum build performance. Techniques like GitOps are unsustainable at a certain number of engineers/commits per hour.