Closing Keynote
summary
Argues that code mirrors team communication and that software is interior space, not a finished building; cites Conway's law, a five‑engineer example with five services, Heartbleed as infrastructure pain, and comparison of Ember AngularJS and React as different “floor plans.” Recommends three concrete norms: don't make it worse, prefer incremental improvements over consistency, and refactor as part of stories, plus negotiate changes with non‑dev stakeholders. Offers hoarding analogy and continuous deployment frequency to show why one‑off rewrites fail.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:39Conway's Law
- 5:50Your Code Will Recapitulate Your Team's Communication Structure
- 9:42Creating a Building
- 11:04Heartbleed Vulnerability
- 25:52Value Improvements
