Tactics and strategies on software development: how to reach ...
summary
Claims that rewriting systems for novelty fails long term and that microservices alone don’t fix evolutionary fragility; cites the Knights/Capital outage as a $460M mistake caused by missing docs. Recommends concrete practices: use C4 diagrams like a Google Maps, ADRs, doc-as-code with AsciiDoc/Hugo and Git, OpenAPI/Swagger for APIs, and measurable testing: mutation testing shows >50% of tests are ineffective so combine with coverage. Notes an example metric: documentation cuts onboarding from two months to one week and cloud often wastes ≈35% of spend.
AI-written summary · about
chapters (11)
- 0:00Introduction and success in software
- 3:01Common obstacles in software development
- 7:42Engineering tactics and strategy
- 13:44Domain-Driven Design basics
- 15:27Documentation trade-offs and importance
- 25:05C4 model for architecture documentation
- 33:01Testing methodologies and quality
- 35:32Cloud costs and inefficiencies
- 41:34Strategy vs tactics in software
- 46:18Simplicity and evolutionary architecture
- 47:25Q&A session
related talks
57mBuilding Systems that are #neverdone
46mArchitecture & DevOps
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
41mThe lost art of software design
36mFrom Software to Systems: Modern Agility
21mAutonomous Teams
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
57mStop writing software like it's 1999!