title	conference	date
on the C4 model	DDD Europe 2025	2025-06-02
C4 evolves from hands‑on teaching to over 200+ clients across 40 countries, offering concrete rules for when to use component versus container diagrams, how to… Talk on
The C4 model: misconceptions, misuses and mistakes	DDD Europe 2025	2025-06-02
C4 defines four abstractions — system, container, component, code — and claims that the real value is the shared vocabulary rather than diagrams alone; common… Talk on
Software architecture as a contributor to high performing teams	Agile meets Architecture 2025	2025-04-03
The session argues that team performance stalls without solid technical foundations and shows concrete fixes: use the C4 model to draw hierarchal… Talk on
Reverse-engineering Architecture Diagrams	Jfokus 2025	2025-02-03
A workflow that actually generates component-level C4 diagrams by scanning compiled Java classes and optionally the source produces clear, maintainable output… Talk on
Visualising software architecture with the C4 model	Porto Tech Hub Conference 2024	2024-11-26
Most architecture diagrams are “boxes and lines” chaos, so C4 prescribes four concrete abstraction levels — System, Container, Component, Code — and shows how… Talk on
Five things every developer should know about software architecture	Build Stuff 2024	2024-11-13
Argues for a modest amount of upfront design focused on decisions that are costly to change later, uses C4 model diagrams and Structurizr (model-as-code) to… Talk on
The C4 model for visualising software architecture	Voxxed Days Thessaloniki 2024	2024-10-18
C4 defines four concrete abstraction levels — Context, Containers, Components, Code — and insists diagrams match the code so maps stop being lies. It models an… Talk on
The C4 Model – Misconceptions, Misuses & Mistakes	GOTO Copenhagen 2024	2024-09-30
C4 defines four hierarchical abstractions — context, containers, components, code — and recommends most teams start with the top two levels; common mistakes… Talk on
The C4 Model – Misconceptions, Misuses & Mistakes	GOTO Amsterdam 2024	2024-06-10
C4 defines four concrete abstractions — software systems, containers, components, code — created around 2007 and intentionally unchanged; it’s notation- and… Talk on
Five things every developer should know about software architecture	Voxxed Days Bucharest 2024	2024-03-27
Argues for just enough upfront design that fixes only the decisions costly to change — language, frameworks, data storage and decomposition — then proves… Talk on
C4 models as code	NDC Porto 2023	2023-10-16
Argues that C4 should be modeled not hand-drawn, and demonstrates the open-source Structurizr DSL plus a renderer (structurizr-light) that stores a single… Talk on
C4 models as code	NDC Oslo 2023	2023-05-22
Introduces a text-first, model-based C4 workflow that produces reusable diagrams from one canonical source: Structurizr DSL defines people, systems, containers… Talk on
C4 models as code	Craft Conference 2023	2023-05-18
A text-first C4 workflow is demonstrated: a single Structurizr DSL file becomes a reusable model (people systems containers components) that generates multiple… Talk on
C4 Models as Code	YOW! Melbourne 2022	2022-12-08
Shows how the C4 model becomes a maintainable, testable model rather than a stack of images: use the Structurizr DSL as a single workspace.dsl to define people… Talk on
C4 Models as Code	YOW! Melbourne 2022	2022-12-08
Presents a practical model-as-code workflow: author a single Structurizr DSL workspace (people, systems, containers), render with Structurizr Lite, export via… Talk on
The lost art of software design	Agile meets Architecture Berlin 2022	2022-09-06
Argues that some upfront design is necessary to avoid costly refactors, recommends drafting a system context diagram and a container diagram (C4 model) as a… Talk on
Diagrams as code 2.0	JNation 2022	2022-06-07
Argues that modeling beats drawn diagrams by creating a single source of truth: a Java-based Structurizr DSL model describes elements and relationships once… Talk on
The Lost Art of Software Design	Devnexus 2022	2022-04-12
Many teams stop at vague whiteboard sketches that score “7 out of 10” in workshops and then rush to code, which produces brittle systems and surprise rework. A… Talk on
Diagrams as Code 2.0	GOTO Copenhagen 2021	2021-11-08
Argues for a model-first approach where a single workspace model and view definitions generate consistent diagrams across formats, not one text file per… Talk on
5 Things Every Developer Should Know about Software Architecture	GOTOpia November 2020	2020-11-10
Argues that teams must do just enough upfront design — identify high‑risk decisions, run concrete experiments/proofs of concept, and stop when scope, key… Talk on
Visualising software architecture with the C4 model	Agile on the Beach 2019	2019-07-11
Argues most architecture diagrams are useless boxes and lines and proposes the C4 approach: four concrete levels — C4: context containers components code —… Talk on
Modular Monoliths	GOTO Berlin 2018	2018-10-31
Argues that you can get microservice-like modularity inside a single Java monolith by aligning architecture diagrams with code, using the C4/Structureizr… Talk on
Visualise, document and explore your software architecture	NDC Oslo 2017	2017-06-14
Advocates a specific, hierarchical approach: C4 model (system → containers → components → classes), plus lightweight docs-as-guidebook limited to what code… Talk on
Visualise, document and explore your software architecture	NDC London 2017	2017-01-16
Claims that teams should model architecture with a small, consistent vocabulary and generate diagrams from a code-backed model rather than hand-drawn Visio… Talk on
Visualise, Document & Explore Your Software Architecture	GOTO Copenhagen 2016	2016-10-03
Argues for treating architecture diagrams as navigable maps and demonstrates an executable architecture description language: open‑source libraries for… Talk on
software architecture vs code	O'Reilly Software Architecture Conference 2015	2015-03-16
Argues that architecture must be visible in code and offers concrete practices to achieve it: use an architecturally evident coding style, enforce naming and… Talk on
Software Architecture vs Code	GOTO Amsterdam 2014	2014-06-19
Argues that architecture must match code and shows a concrete C4 style workflow from context to containers to components using a real open sourced content… Talk on
Software Architecture vs Code	GOTO Chicago 2014	2014-05-20
Argues you must make diagrams match the code and shows a practical way to do it: use the C4 model (system → containers → components → classes), build maps that… Talk on
nothing matches

-- 28 of 28 talks indexed --