Corporate programming is typically bent towards feature delivery and managing patches. Only feature delivery requires managing a project, but it's not new devel

Corporate programming is typically bent towards feature delivery and managing patches. Only feature delivery requires managing a project, but it's not new development scale. It involves one or two engineers at most, and anything that requires greater resources than that are looked at skeptically. It's my opinion that this puts us heavily out of practice. Instead, I'd like to engage in work that is outside of our core business. I want to build our own dev tools at times, I'd like to run our own infra rather than toss it at Amazon, Google, or Microsoft and point the finger when it breaks. Having to work outside of a product we know inside and out, domains we're already very familiar with, will improve residual skills like documentation. The repetition of doing and the variety in what we do makes skilled and well-rounded engineering teams imo.