Fighting Software Entropy
summary
Company adopts architectural principles, an internal tech radar, quarterly system health ratings stored in BigQuery and published via CI, and 20% custodianship capacity to fight decay. Automation uses Renovate and scheduled CI/CD builds; platforms (Argonaut, React-based) cut template code ~35%, developer effort ~75%, and custodianship needs ~90%. Health is rated green/amber/red (default unhealthy), with practical criteria for dev/ops/architecture and a Ship quarterly process to prioritize objective fixes.
AI-written summary · about
chapters (16)
- 0:00Intro
- 2:43What is entropy?
- 3:55What is software entropy
- 11:18How can we fight software entropy?
- 11:40Architecture practice
- 19:04Key takeaways
- 19:41Engineering excellence
- 28:22Key takeaways
- 28:48Continuous improvement
- 34:34Key takeaways
- 35:07Adopting platforms
- 39:53Key takeaways
- 40:30Recap
- 40:55Key takeaways
- 41:49Outro
- 42:00Q&A
related talks
28mThink Backstage! Beyond Plugins
43mCode quality as an engine of your IT business
42mFrom Chaos to Control, from Control to Freedom
58mKeynote: Seven Habits of a (Mostly) Successful Team
48mTechnical Enshittification: Why Everything in IT is Horrible Right Now and How to Fix It
40mPractices from trenches for embracing evolutionary architecture in wild
18mAgile leadership and technical mastery, a harmonious alliance
15mTaming software sprawl and demystifying your distributed architecture (PRT032)