วีดีโอ

th-cam.com/video/x2-rSnhpw0g/w-d-xo.html

I found out about C4 thanks to a job interview, and now I am implementing it to design some processes, and I love it.

This is the best thing for creating diagrams... even after 5 years

I told Clara this at the conference -- one of the most thought-provoking talks at Agile on the Beach, which had a lot of great talks. I took as many "I need to really ponder this" and "let's talk about this as a team when I get back" notes as I ever do. Recommend & thanks, Clara.

If only my surname was Brain 😂😂 when it’s actually Brian

Forget about SCRUM, forget about rigid rules and rituals. Just focus on this, always: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

Thanks for having me! It was a pleasure speaking at AOTB 2024! ❤

That was an amazing talk, i enjoyed every second of it !!

A very detailed and very useful explanation about C4 Model. Thanks.

What a bunch of nonesense.

This was such a great talk, thanks so much for sharing Derek!

"We were not telling them a lie" <=> "We were telling them the truth".

Thanks to Agile on the Beach for having me, putting on such a great conference, doing such good recordings, and thanks to everyone who attended!

10:01 I'm a Studd developer.

Guess what...I don't agree with pope or your picture of what racial discrimination is, but you are literally discriminating me for being white. Now what?

What a great presentation. Thank you Simon

@MilanJovanovicTech Hope you can write your next blog around documenting your Modular Monolith with C4 models. :)

“UML notation is too complicated” Yes, I see that when design a DB. Merise, yep, the oldie, is easier to understand for an audience. Even devs. I reckon UML tried to be a jack of all trades making it….. a tad over complicated in some cases.

Great to see you representing RR and sharing our story on an agile conference!

love the pragmatism! so true that agile has given people an excuse to simply stop using UML. i blame atlassian adopters mainly; they should have screamed absolute bloody murder when jira lacked the functionality for use cases. what a crying shame. If you remember, back in 2000 nearly everyone in I.T. had gone absolutely nuts over UML and Cockburn's purple book, and primarily for just one of the concepts, and that was the Use Case. Finally we all had something that closed the gap between System Requirements (what the Users and SME's needed) and Functional Specs (what the devs gave them.) Use Cases -- simply describing in words the actual behaviors of actors and system components -- was simply brilliant, and a gazillion times better than clunky Requirements documents, which Software Engineering folks had always interpreted one way (apples), while Test Engineering interpreted another (oranges). Why the hell people would let this slide and accept the sub-par "User Story" (AKA scribble on a sticky note) is beyond me. It reminds me of how distributed/redundant systems caught on and everyone went crazy over microservices, yet they were perfectly fine with the ENTIRE system being dependent on a single service. In the latter case the CrowdStrike debacle will likely make them self-correct, but unfortunately nothing can force people to do effective UML, Process, or even communicate at all for that matter.

what about the file and directory structure? Robert Martin talks about that. Although I think he did server side programming which is a lot easier than programming where you have to keep track of state. It's almost like maybe other languages should copy server side programming so you don't have to keep track of state. However I think Javascript got rid of that so that you have to keep track of state without concurrency. We need some criteria by which to choose good design. Design should make it easier to add features, easier to fix, it should allow the software to run faster. It should be more secure. it should be easier to fix by third parties. It should be easier to add features to by third parties. It should be as small as possible. It should be compatible with the most systems. There may be more requirements. There will be specific requirements. How can it's design serve those requirements?

9:35

th-cam.com/video/x2-rSnhpw0g/w-d-xo.html Most people hate it as they don't it well. Out industry is now full of people who are restless and wants to take shortcuts. They don't have the complete knowledge, but they just judge it. It's what boys and girls do in their teen years. So the industry is full of immature people.

Brilliant

Great!

Does anyone have the slides? The link above is dead. Thanks in advance.

Great! Excellent content and presentation skills!

I use OmniGraffle mostly and it's perfectly fine.

Thanks for sharing!

Still awesome in 2024! What a great presentation and explanation to break down such a complex ways of communication into simple process.

One of the best presentation not just in terms of delivery and content, but also impact🎉

16:30 Margy Ross of DecisionWorks

Great demo. You can also use Miro boards, if you don't want your sticky notes fall off.

Yeah, I think I need to come to AotB24 now

“SHIA LABEOUF” is a song by Rob Cantor. It tells the true story of an actual cannibal. th-cam.com/video/o0u4M6vppCI/w-d-xo.html

great video

nice mr simon brown, you are inspired us to create content about software architect for our college in UINSA, thanks a lot #amflearning #amflearningbydoing #amfedukasi #amfedukasiforeveryone

Exactly what I'm looking for. Thanks a lot

Really excellent talk. Glad that AotB is publishing these so I was finally able to catch this, too. Multi-track conferences almost always end up scheduling the things I want to watch at the same time 😆 Anyway, I've been inspired by this to actually go and do some writing!

so good presentation

C4 model Context = System (but Context is fine too) Container = Component Component = Module Code = Code I guess the weird naming, is to be able to call it C4 instead of SCMC

This is really stupid, even Agile is better.

what's the advantage of using C4 over uml ?

really cool, thnx!

Sadly the slides captured don't show the several animations of objects moving across the boards, but hopefully the narration makes sense.

One major problem is that his software-architectural floorplan diagram is actually brilliant.

This is awesome. Wish I saw this talk earlier!

Really great presentation!

This can't get any more dishonest. Examples for bad modelling carefully chosen to include obvious works in progress, general ideas or helicopter views, with crossed out names, written on wrinkled paper. You spent no time to try to explain those, yet you've spent quite a bit to explain what you have modeled in C4, even though it was supposed to be so clear. And you've done multiple levels of presentation of your design and did not compare those to any other techniques. Absolutely nothing new here, just promoting old design under a new name.

Quite informative, thanks!