ISBN: 9798198978539 - the 36 stratagems for software teams: ancient strategy patterns for engineering, product, security, and delivery (4 risultati)

Lingua: Inglese
Editore: Amazon Digital Services LLC - Kdp, 2026
- Brossura
- Print on Demand
Da: PBShop.store US, Wood Dale, IL, U.S.A.PBShop.store US
Contatta il venditoreVenditore con 5 stelleCondizione: Nuovo
EUR 11,28
Spedizione gratuitaSpedito in U.S.A.Quantità: Più di 20 disponibili
PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Lingua: Inglese
Editore: Amazon Digital Services LLC - Kdp Mai 2026, 2026
- Brossura
Da: AHA-BUCH GmbH, Einbeck, GermaniaAHA-BUCH GmbH
Contatta il venditoreVenditore con 5 stelleCondizione: Nuovo
EUR 22,58
EUR 35,00 spedizioneSpedito da Germania a U.S.A.Quantità: 2 disponibili
Taschenbuch. Condizione: Neu. Neuware - 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 decisionsEach 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 awayPart 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.…

Lingua: Inglese
Editore: Amazon Digital Services LLC - Kdp, 2026
- Brossura
- Print on Demand
Da: PBShop.store UK, Fairford, GLOS, Regno UnitoPBShop.store UK
Contatta il venditoreVenditore con 5 stelleCondizione: Nuovo
EUR 10,52
EUR 3,89 spedizioneSpedito da Regno Unito a U.S.A.Quantità: Più di 20 disponibili
PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Lingua: Inglese
Editore: Independently Published, 2026
- Brossura
- Print on Demand
Da: CitiRetail, Stevenage, Regno UnitoCitiRetail
Contatta il venditoreVenditore con 5 stelleCondizione: Nuovo
EUR 14,60
EUR 43,73 spedizioneSpedito da Regno Unito a U.S.A.Quantità: 1 disponibile
Paperback. Condizione: new. Paperback. 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 indirectlywhen to wait, contain, simplify, or retreathow to handle migrations without creating unnecessary disruptionhow to use prototypes, feature flags, rollback paths, and stable interfaceshow to recognize hidden risks in tools, vendors, dependencies, and architecturehow to turn incidents, uncertainty, and technical debt into better decisionsEach 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 modernizationrelease planningincident responsedependency riskplatform adoptiontechnical debtsecurity controlsteam coordinationproduct and engineering tradeoffsknowing when to stop, rollback, or walk awayPart 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. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…