3 ms·
> Today, the theme is CI/CD, which translates into "figure out how to keep an overstaffed engineering department occupied long after they delivered the working
by Terr_ 3y ago
> Today, the theme is CI/CD, which translates into "figure out how to keep an overstaffed engineering department occupied long after they delivered the working system". [...] with the intention to keep the department occupied
I disagree on this causal part: That malaise does not exist because Machiavellian engineers created a job-security program stealthy enough to persistently escape action from bean-counting executives.
Instead, it's caused because other business stakeholders are paying a premium in order to avoid deeper commitment of some sort.
A few examples:
* They want to avoid the risk of a big innovative product that may be a similarly-big flop.
* They can't bear to drop any customers by streamlining the product, always adding bells and whistles to appeal to the potential client du jour.
* They are unable/unwilling to spend/risk political capital in substantially altering how their own corporate structure operates.
* The company's leadership isn't capable of making different business-units work in harmony so the software becomes a slow battleground/mediator of their competing interests.
- bane 3y agoI actually don't disagree with you on any point. But I do think the relationship can become an unhealthy codependency that causes organizations and developers to lack the discipline that would be more ideal.