A lot of tech books focus on a steady state. Use this for that job, have 8 engineers per team and put two on calls every week, micro service and kubernetes ever

A lot of tech books focus on a steady state. Use this for that job, have 8 engineers per team and put two on calls every week, micro service and kubernetes everything, do DevOps, automate every bit of CI/CD etc. The thing is, it really depends on what stage you are in. Evolve your organisation accordingly, there is no one size fit all solutions. How did a river form? Don't blindly build a river. Otherwise you become the fish that swims within never realising how you come there in the first place. Notable exception is mythical man month. It describes transitions rather than steady states which put a lot of things into perspective imo. Having said that, engineering books do provide a map of reality. A map is a map. That goes a long way