Still relying on confusing architecture diagrams? 🏗️
Attend Simon Brown's hands-on workshop at #Dev2Next to learn why most diagrams fail, how to fix them, and how the C4 model can help you create clearer views of your software systems.
🔗 https://www.dev2next.com/schedule
🎟️ Get tickets: dev2next.com
#SoftwareArchitecture #C4Model #Developers #Software #Architecture #DeveloperWorkshop
I finished modeling the architecture for Xenguard. My reluctance in using UML & Co. pushed me to find alternatives and to my surprise modeling then became much fun suddenly!
I wrote a few words on my modeling journey:
Modeling is an integral part of software engineering. Yet, proper models for software projects are hard to come by. Why is that? I have a theory about why software engineers are reluctant to model software, and I have also found a solution to overcome modeling hurdles for Xenguard.
#SoftwareArchitecture diagrams are one of the clearest ways to communicate - whether you’re building something new or documenting existing systems for knowledge sharing and learning.
Simon Brown’s #C4Model, featured in a 2018 #InfoQ article, is one of the most practical approaches to keeping architecture documentation simple, consistent & useful.
This classic framework is as relevant today as ever!
🔗 Read now: https://bit.ly/479pkKY
#InfoQ20 #Diagramming #ArchitectureDocumentation #SoftwareDevelopment
The #c4Model is a way to communicate #SoftwareArchitecture at different levels of abstraction.
You can tell different stories to different audiences - it's a way to introduce rigor & lightweight modeling to software development teams.
Dive deeper on #InfoQ 👉 https://bit.ly/479pkKY
#Diagramming #ArchitectureDocumentation #SoftwareArchitectureDiagrams
Unit tests used to feel like a struggle—now they’re my guardrails. Writing documentation? Same story. I share how I turned these dev “chores” into habits that give me speed and confidence. With the C4 model, documentation doesn’t have to be hard. Start small, stick with it, and watch your workflow transform. 🚀
Every time I joined a new project, I made it a point to take responsibility for fixing bugs. Why? Because fixing bugs is the best way to understand the architecture and get familiar with the codebase. Often, there’s little to no documentation, and all the knowledge is locked inside the developers’ heads. By fixing bugs (and writing tests as I went), I created my own map to navigate the codebase, uncover its quirks, and ensure I wasn’t lost.
📁 #FromTheArchive - The #c4Model is a way to communicate #SoftwareArchitecture at different levels of abstraction; you can tell different stories to different audiences. It's a way to introduce rigor & lightweight modeling to software development teams.
Read on #InfoQ: https://bit.ly/479pkKY
#Diagramming #ArchitectureDocumentation #SoftwareArchitectureDiagrams
Ever wondered how #Decathlon ensures its teams are well-equipped to make informed, strategic decisions?
Dive into this #InfoQ #CaseStudy where we explore their use of architecture committees, the #C4Model, #SystemThinking, and #ArchitectureDecisionRecords (ADRs).
We spoke with Raphaël Tahar to uncover Decathlon's architecture process, the challenges faced, and the organizational impacts: https://bit.ly/3Ah25T6
Planning to run #structurizr on your own #Windows PC and wondering what all you need to do to be able to draw #C4Model pictures using #DiagramAsCode?
Here's the list of what I did!
Should I do a blog post? Follow to find out when it gets done
#TIL: #Freemind will happily create a #mindmap from tab-delimited text pasted into it!
Really helps to get a mindmap from my notes about the book on using #C4Model for visualising software architecture. Next step: @structurizr
dev2next
Pouyan Fotouhi Tehrani
InfoQ
Grzegorz Wilczyński
Mohit Sindhwani
Benny from the Block