Move Thoughtfully and build things
summary
Argues for trading "move fast and break things" for move thoughtfully and build things, showing why large-scale projects need discipline: the Tacoma Narrows bridge failure lacked aerodynamic testing and collapses, cathedral construction illustrates centuries‑lasting coordination and precision, and a weak DMV password cost tens of thousands in identity theft. Recommends concrete practices: prioritize people, add wind/aero and security tests, teach and mentor within Java communities, measure user impact, and design for stability and evolvability.
AI-written summary · about
chapters (14)
- 0:00Welcome and introduction
- 1:15Why people matter most
- 3:41Lessons from Cologne cathedral
- 5:48When precision fails in engineering
- 8:46Human cost of invisible software
- 10:12Critique of move fast and break things
- 12:41Real life impact of poor design
- 14:28Move thoughtfully and build things
- 16:18People first technology second
- 17:43Overcoming imposter syndrome
- 19:50Java community and mentorship
- 21:39Reinvesting in yourself and others
- 24:05Collaboration for Java's future
- 25:48Closing call to action
related talks
43mThinking Architecturally
25mThinking Architecturally
48mMove Slow and Mend Things
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
44mDeliberate Architecture
08mLightning talks – 101 Things Software Never Learnt
49mCultivating Architecture
01h 02mThinking Like an Architect