Fighting software entropy
summary
Company-wide playbook for keeping long-lived systems usable: define objective system health criteria and run quarterly health ratings and audits, back them with automation so answers are verifiable; allocate a 20% custodianship budget per team and embed architects with 20% central time to reduce divergence; publish an internal tech radar for sensible defaults and steer teams to platforms that cut effort (example: a web platform that yields ~35% less code, ~75% less developer effort, ~50% faster time to market).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47Maintaining software at scale
- 3:30Software entropy analogy
- 5:39Architecture reduces entropy
- 11:42Architecture principles
- 19:54Aligning architecture to reduce entropy
- 21:20Engineering excellence definition
- 27:40Continuous improvement
- 36:27Platform strategy for complexity
- 39:35Summary
- 40:18Q&A
related talks
54mDeveloper experience platforms
20mThe road to developers' hearts
44mEnhancing the Performance of Engineering Teams
50mTactics and strategies on software development: how to reach ...
15mTaming software sprawl and demystifying your distributed architecture (PRT032)
11mLeading without committing: Managing teams outside your tech stack
01mFor the Love of Software
52mUnderstanding UnHealthy Syndromes of Software Delivery