Overview

Ancient strategy. Modern software problems. Practical engineering judgment. Software teams rarely face neat textbook problems. They face risky migrations, fragile releases, noisy incidents, unclear ownership, vendor hype, technical debt, security pressure, and roadmaps shaped by both code and humans being human. The 36 Stratagems for Software Teams takes a classic Chinese set of strategic patterns and reimagines them for modern engineering, product, platform, security, and delivery work. This is not a book about manipulation, office politics, or pretending sprint planning is an ancient battlefield. Instead, it uses the Thirty-Six Stratagems as a practical lens for recognizing patterns that software teams already deal with every day: when to move directly and when to move indirectly when to wait, contain, simplify, or retreat how to handle migrations without creating unnecessary disruption how to use prototypes, feature flags, rollback paths, and stable interfaces how to recognize hidden risks in tools, vendors, dependencies, and architecture how to turn incidents, uncertainty, and technical debt into better decisions Each chapter explains one stratagem in plain language, then connects it to a realistic software-team situation using examples from architecture, platform work, delivery, operations, security, and leadership. You will find practical lessons on: legacy modernization release planning incident response dependency risk platform adoption technical debt security controls team coordination product and engineering tradeoffs knowing when to stop, rollback, or walk away Part of The Practical Tech Guide Series, this book is written for engineers, tech leads, engineering managers, product managers, platform teams, security teams, and founders who want a sharper way to think about messy technical decisions.

Full Product Details

9798198978539

Table of Contents

Reviews

Author Information

Tab Content 6

Countries Available