From big to small and back again
summary
Argues that high-quality delivery (continuous integration, CD, XP, automated tests) still fails when context is missing, showing concrete failures: a CRM rollout replaced by Siebel after an IPO, a 57,000-line pricing routine on a mainframe, a firm that acquires 140 companies creating hidden complexity, and a system with 10 downstream systems deployed in sequence. Recommends using impact estimation and information maps to surface business objectives, constraints and user flows (hospital IV error rate ~50%), so architecture and product choices reflect real information and operational needs.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:13Disclaimer
- 8:22Impact Estimation
- 12:08Architecture and Documentation
- 13:41Insanity Situations
related talks
27m“Good Enough” Architecture Part 2
57mSoftware Architecture: The Hard Parts
48mAgility in Large Transformation Programs – An oxymoron?
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
55mContinuously Delivering Continuous Delivery
33mFrom Enterprise Architecture to Software Design - Critical Thinking
44mThe Art of Architecting for Scale
01h 29mMonolithic Delivery