SW Design, Architecture & Clarity at Scale

on YouTube ↗45m

" summary

Panel argues that lightweight Decision Records (short or long templates, draft status for collaboration) plus automation and placement where teams already work turn decisions into usable artifacts; shows ACE model for slicing design through context and architecture; cites a 3,000‑person org with 800–900 developers to justify repeated comms and platform engineering; recommends using OpenAPI for live API docs and observability plus scheduled feedback loops to detect when to supersede decisions.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 2:46What is software design?
3. 4:21Decision‑Records: Why & how to use them
4. 22:46Keeping documentation fresh – ADR templates & automation
5. 29:44Bridging the Dev ↔ Architect gap
6. 32:30Standardizing vs Over‑standardizing (Platform Engineering)
7. 42:20Feedback loops & continuous improvement
8. 45:00Outro

" related talks

• 30mCommunicating and documenting architectural decisionsDavid Ayers · The Lead Developer New York 2019
• 42mDecision-making for developersRick Kuipers · phpday 2024
• 26mHow a team that communicates well collaborates wellMathias Meyer, Sara Hicks · LDX3 London 2025
• 16mEveryone architect!Simon Maurin · Devoxx France 2023
• 41mThe lost art of software designSimon Brown · Agile meets Architecture Berlin 2022
• 39mOne Does Not Simply Make Architecture Decisions Alone: ADRs and ArchitecVladas Diržys · Build Stuff 2025
• 30mJames Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023James Stanier, Winter Wi, Janet Balneaves · LeadDev London 2023
• 32mWriting design docs for wide audiencesMichele Titolo · RailsConf 2021