[VDBUH2024] - Simon Brown - Five things every developer should know about software architecture

The software development industry has made huge leaps in recent years, yet software development teams are often more chaotic than they are self-organising, with the resulting code being more of a mess than was perhaps anticipated. Successful software products aren’t just about good code, and sometimes you need to step away from the IDE for a few moments to see the bigger picture. This session is about that bigger picture and is aimed at software developers who want to learn more about software architecture, technical leadership, and the balance with agility. This talk will debunk some of the common myths as we look at five things every developer should know about software architecture - a guide to modern software architecture that’s pragmatic rather than academic and lightweight rather than “enterprisey”.

[@TechTalksWeekly]

Simon's talk has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

[@chekolino88]

1. Architecture isn't about big design up front
2. Every team needs technical leadership
3. The software architecture role is about coding, coaching and collaboration
4. You don't need to use UML
5. A good software architecture enables agility

[@sunwicked]

Good stuff

[@batousay6437]

In minute 10:15 aprox, when he's speaking about Risks I didn't quite get the name of the book/process. Does someone understood it and can write it down for me? Thanks.

[@chekolino88]

Simon said: "I have a technique and you can find it online, it's called Risk-storming".