Talks to Watch

Visualising software architecture with the C4 model - Simon Brown, Agile on the Beach 2019

554K views · Aug 16, 2019 · 35:33 · 3 HN recommenders · 4 mentions · discussed 2021–2023

Simon Brown's Agile on the Beach 2019 talk presents the C4 model, a lightweight approach to diagramming software architecture with a shared vocabulary and simple notation.

Why Hacker News points people here: Recommended as the introduction to C4 when people ask how to visualize and communicate software architecture.

“If C4 is new to you too, I recommend their intro video”HN comment, 2023

What Hacker News said 4

RecommendstmountainNov 2021

“I recommend the C4 model.”

Introduces C4 model for coherent architecture diagrams

Full comment

These fail my litmus test, which is, "can a third-party look at the diagram and make sense of it without verbal explanation?" For a more formal approach to coherent diagrams and white boarding, I recommend the C4 model. It's conceptually simple and results in better system documentation than the free form method that's commonly used. this video

in “Beyond Whiteboarding: Creating Expert System Architecture Diagrams” · view on HN
RecommendsqrianMay 2022

“which seemed very promising.”

Introduces the promising C4 model

Full comment

Recently stumbled upon [C4 Model]( this video ), which seemed very promising. It builds on the failure of adopton of UMLs, and aim to be practical and communicative.

in “Ask HN: Visualizing software designs, especially of large systems (if at all)?” · view on HN
RecommendsSnowProblemAug 2023

“If C4 is new to you too, I recommend their intro video”

Intro to C4 as a light ruleset for system diagrams

Full comment

If C4 is new to you too, I recommend their intro video: this video . It feels like a very light ruleset over what we would do naturally when explaining a system to another engineer. That's great. Some of the ideas that stood out were: 1. Allow flexibility in the notation (shapes and color) as long as the abstractions are good. 2. When drawing arrows, make them unidirectional to show the main intent. 3. Hide details to express the main story (@ 27min in the video) 4. Don't just give names to components. Give short descriptions too. 5. Don't document the lowest levels. Code is better here.

in “Architecture diagrams enable better conversations” · view on HN
Cites itchrsigJan 2023

“the author of structurizr (Simon Brown) was recently linked in another HN thread.”

Talk by the author of structurizr

Full comment

I've looked at mermaid & planetuml before. structurizr is new to me and looks interesting. PlanetUML has the advantage of gitlab support, iirc -- allowing rendering of diagrams in README files. I'd like to see more options for that. edit: interestingly, the author of structurizr (Simon Brown) was recently linked in another HN thread. HN thread - link YT link - this video

in “Architecture diagrams should be code” · view on HN