5 Things Every Developer Should Know about Software Architecture • Simon Brown • GOTO 2020

This presentation was recorded at GOTOpia November 2020. #GOTOcon #GOTOpia

Simon Brown - Creator of C4 Software Architecture Model & Author of "Software Architecture for Developers" @simonbrown4821

ABSTRACT
The software development industry has made huge leaps in recent years, yet software development teams are often more chaotic than they are self-organizing, with the resulting code being more of a mess than was perhaps anticipated.
Successful software projects 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 aimed at software developers who want to learn more about software architecture, technical leadership and the balance with agility [...]

TIMECODES
00:00 Intro
00:25 1. Software architecture isn't about big design upfront
10:24 2. Every software team needs to consider software architecture
12:35 3. The software architecture role is about coding, coaching & collaboration
17:31 4. You don't need to use UML
24:32 5. A good software architecture enables agility

Download slides and read the full abstract here:

Check out our upcoming masterclasses with Simon Brown here:

RECOMMENDED BOOK

#SoftwareArchitecture #Architecture #C4Model #Backend #Culture #Agility #AgileSoftwareDevelopment #SimonBrown

CHANNEL MEMBERSHIP BONUS
Join this channel to get early access to videos & other perks:

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[GOTO-]

Looking for books & other references mentioned in this video?
Check out the video description for all the links!

Want early access to videos & exclusive perks?

Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇

[abccool]

This is one of the best discussion on software architecture I’ve heard so far

[avibrarbrar]

After watching this video I went on to read a book about architecture - opened this book named Software Architecture for developers and as I started reading the book then I realized it's a Simon Brown book...what a coincidence. Really good content. Thankyou.

[DodaGarcia]

6:04 - “lol I’m two steps ahead of him, I’ll just start with a well-designed, decoupled monolith and then convert it to microservices”

6:31 - “oh”

[coderider]

My current company is obsessed with UML diagrams for EVERYTHING and it drives me crazy. Something that I did in education in 90s and it should have stayed there.

[Reaper]

"A good software architecture enables agility" this is something I've thought about in the past couple of weeks, and it's lead me to ask the question, "How does our architecture support our way of work?"

[samehsz]

Awesome presentation Simon. How architecture affect the Lead Time?

[reactiveland]

I like to add that there is no architecture or architect as higher in hierarchy.
Only levels of abstraction or angles of focus. Neither 🦉 nor 🐸 are more important. So focus on solution rather than roles.

[frotes]

Really great talk! Touches on many important points of software architecture

[moshecsbgu]

Very good talk. It reveals misconceptions about the subject and delivers good advice

[CoxJul]

"You don't need to speak English" - of course not, but if everyone speaks that language it's a good idea, even if it's their second or third language. The problem is, if people just know words but don't understand how to use them properly to create meaningful sentences then poor communication occurs. The same with most people's use of UML.

[valour.se]

If you can't understand the boundaries / bounded context, you will suffer in microservices, even if you are writing a monolith which you think you are going to break into micros.

[MaxLaurieHutchinson]

I like it, it suits my principles: "The software architecture role is about coding coaching and collaboration"

[OmPrakash-zynw]

I believe while design once should be able to define macro vs micro decision.

[bartoszpiekny]

Good talk. I feel that majority of the topics comes from the Craig Larmans book.

[willemvdk]

Excellent talk! It reminds me of a very good book I read on a quite regular basis that touches on these subjects many times: Code Complete by Steve McConnell. Really good read!

[logiciananimal]

Risks are subjective? No. What to *do* about them can be and sometimes should be, however. Rest of the talk is excellent, however.

[TNothingFree]

Great talk!
Recommended to anyone who doesn't have much experience with design :)
Especialy with the UML thing, I've met some people who used more UML and it gets very confusing very fast.

[maksimbober]

A good architecture enables agility, but this agility would need to be an actual one and not imagined (overgeneralizing for too many cases).

[dvanrooyen]

Cost to change is a bad example because something could be super critical and important to a system but fairly cheap to change.

Hard to change is a better example