Agile Engineering: The Hard Parts
summary
Argues that architectural governance must be automated using fitness functions (unit-test‑like checks) and shows tools: JDepend/ArchUnit/net‑archtest for package and layer rules, Pact for consumer‑driven contracts, and Netflix’s Chaos Monkey family (including Conformity and Security Monkey and the janitor monkey) to enforce resiliency and cleanups. Advocates trunk‑based development with feature toggles instead of long feature branches, cites GitHub’s Scientist experiment (10+ million comparisons over four days) and claims pairing slows output ~20% but yields ~80–90% higher quality.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 1:02Automation in agile engineering
- 2:05Automating architectural governance
- 8:46Fitness functions explained
- 15:12Real-world fitness function examples
- 23:24Pair programming deep dive
- 36:30Feature branching vs toggles
- 45:13Feature toggle best practices
- 51:10Incremental architecture change
- 55:25Case study: GitHub’s Scientist tool
- 58:16Closing remarks
related talks
50mBuilding Evolutionary Architectures
38mAgile Architecture
41mOrganising and Governing Evolutionary Architectures (Fitness Functions)
01h 00mEvolutionary Architectures
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
01h 00mAgile Architecture
48mDown the Ivory Tower towards Agile Architecture
33mBuilding Evolutionary Architectures