Fredrik talks to Barry O’Reilly about software architecture.
Barry has spent a lot of time and energy connecting software architecture to actual code and development work, and finding good ways of actually training new generations of software architects.
Architecture is a level above programming, it is a different skill, and it needs to be properly taught so that more people can think and make active decisions about it. Oh, and architecture happens at a group level. You can’t really do it alone.
Barry’s quest led him to complexity science, a PhD to actually prove his ideas hold up, and two books. The idea that you have to understand what goes on in the code in order to do good architecture is more controversial than one might think.
Thank you Cloudnet for sponsoring our VPS!
Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at [email protected] if you want to write longer. We read everything we receive.
If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi.
Links
BarryBlack tulipComplexity scienceIDEAntifragileNassim TalebNassim guesting Econtalk talking about antifragility while the book was in progressBarry’s papers:No More Snake Oil: Architecting Agility through Antifragility (2019)An introduction to residuality theory: Software design heuristics for complex systems (2020)The Machine in the Ghost: Autonomy, Hyperconnectivity, and Residual Causality (2021)The Philosophy of Residuality Theory (2021)Residuality Theory, random simulation, and attractor networks (2022)Residuality and Representation: Toward a Coherent Philosophy of Software Architecture (2023)Domain driven design EuropeLeanpubResidues - Barry’s first bookBarry’s NDC talks - on process and on philosophySupport us on Ko-fiOur agile release train engineer stickersThe architect’s paradox - Barry’s second bookAccelerateØredevKodsnack 346 - Tomer Gabel about the golden age of tomfooleryDataföreningenDataföreningen kompetensTitles
How we design and think about structureClimbed the greasy poleKeep close to the codeRemove themselves from the code as a status symbolI would see a lot of greyThere’s a generation missingA level of thinking above programmingWhen you look up from your IDEWe had to rescue architectureWhen they say “architect”Headed for that ivory towerA self-titling professionComfortable in uncertaintyMultiple books, and a PhDHow does this thing breakEverything will always breakPatching those cracksDo you have any proof of this?The key to good software architecture is pessimismThe mincing of academic criticismTyping furiouslyHope for the futureHe’s from the real world!