Make technical strategy credible by naming which engineering commitments will end, pause, or lose support when a new priority takes capacity.
A Technical Strategy Needs an Explicit Stop-Doing List
Posted on in Technology Management / Leadership
- Designing Data-Intensive Applications The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
- A Philosophy of Software Design 2nd Edition
- The Staff Engineer's Path A Guide for Individual Contributors Navigating Growth and Change
- The Remote Engineer
- ZaZo Designs