To me the example reads more like a management strategy that is _about_ engineers rather than engineering strategy. Do I fundamentally misunderstand what engin

To me the example reads more like a management strategy that is _about_ engineers rather than engineering strategy. Do I fundamentally misunderstand what engineering means? I would have expected something along the lines of explaining the goals and how to measure things like: - performance, latency and throughput, ball park estimations - robustness and correctness, which parts are critical and prioritized, what kinds of bugs can or cannot be tolerated, when are they being fixed - resource usage, devices/hardware, deployment targets And secondarily perhaps topics like: - protocols and standards to adhere to - open source and dependencies - automation and tooling - dev environments, version control - testing and feedback loops