Automate your software design How far we can get and how the AI chan
summary
Shows how to turn design into code: keep docs and diagrams in the repo, use docs-as-code (Markdown + static site), store Architecture Decision Records as immutable files, and generate diagrams with text syntaxes like Mermaid or PlantUML. Demonstrates scripts that pull config and auto-generate up-to-date maps, integrates C4/Structurizr for scoped views, and uses LLMs to draft ADRs and diagram code — with a concrete caveat: LLM outputs need human verification (example: generated diagram code took seven minutes and required manual fixes).
AI-written summary · about
chapters (13)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:35Introduction: Technology-Agnostic Design Thinking
- 3:20Problems in Software Design: Chaos & Over-Engineering
- 7:00Automation Beyond Code: SDLC Overview
- 11:10Docs-as-Code: Markdown, Repos & Validation
- 15:30Keeping Documentation Updated & Useful
- 19:40Architecture Decision Records (ADR)
- 24:20Diagrams Evolution: Whiteboard → Code
- 28:10Diagram-as-Code (Mermaid, PlantUML, Versioning)
- 32:00C4 Model & Structurizr (Scalable Architecture Views)
- 35:00AI in Design: Capabilities & Limitations
- 38:00Real Workflow: AI + Docs + ADR + Diagrams
- 40:00Final Takeaways: Automate Smart, Stay Intentional
related talks
01h 00mVisualise, document and explore your software architecture
57mVisualise, document and explore your software architecture
51mConsistent architecture diagrams for C++ projects
51mDiagrams as code 2.0
50mCoevolution of Architecture & Code - Closing The Gap
01h 00mC4 models as code
35mRewilding Software Engineering - AI, Tools and Human Decisions
57mDesign Patterns for Software Diagramming
