

Also, when developers have lots of cross-team and cross-skillset coordination that needs to happen, you can spend the majority meeting, documenting, and reviewing.
Case in point; my Cloud team spends a significant chunk of time coordinating between backend and frontend, Ops, Firmware/Hardware team and DevOps.
Product Owner wants a feature, specs how the feature should look in the frontend, and what the device needs to do when used. Backend has to spec the cloud logic and API glue between them. A feature might need support from DevOps if infrastructure needs to be updated, and Ops needs to know how the feature works to support customers.
It’s a whole lot of talk and documentation so that the amount of time we spend coding is as little as possible. That’s a good thing. If you’re spending the majority of your time writing code, you’re probably doing something wrong.
Stability, reliability, don’t fix it if it ain’t broke.
Some companies have a need to reinvent them every 6 months to justify some middle Manager’s existence so they can pad their resume for the next overpaid job position.
This Is what it looks like when you don’t have that problem