Software Architektur im Stream

Eines der unbeliebtesten Themen in der IT ist die Dokumentation. Viele drücken sich davor sie zu schreiben, viele wollen sie nicht lesen. Doch sie bringt uns weiter und ist wichtig. Benjamin Wolf und Gernot Starke beantworten Fragen rund um das Thema Dokumentation. Wie können wir anfangen, unsere Dokumentation zu verbessern?

We all have some ideas about what works in software engineering and what doesn’t. But without real evidence and data that is just an opinion. Empirical software engineering tries to answer the question of what can be proven to work in software development. In this episode, Hillel Wayne and Laurent Bossavit will talk about what we know about software development, what we don’t know - and the myths about it i.e. what we think we know but really don’t.

Links

Additional Links

Am Ende des letzten Jahrhunderts stand Wiederverwendung im Mittelpunkt des Interesses: Dadurch sollte Software-Entwicklung endlich einfach und unfassbar produktiv werden. Nun sind mehr als zwanzig Jahre vergangen und es scheint auf den ersten Blick so, dass Wiederverwendung doch kein erfolgreiches Konzept war. In dieser Episode sprechen wir darüber, was wir in den letzten zwanzig Jahren gelernt haben - und wie Wiederverwendung in aktuellen Projekten stattfinden kann und sollte.

Nachdem es schon einige Folgen zum Thema Frontendarchitektur gab, die eher den Fokus auf Server-seitig gerenderte Architekturen gelegt haben, gibt es nun endlich eine Episode mit Manfred Steyer, die den Fokus auf Single Page Applications legt. Wir sprechen über Modularisierungskonzepte dieser Art von Architektur, wie zum Beispiel Microfrontends und Clients-Modulithen. Außerdem zeigen wir euch Entscheidungshilfen für die Wahl des passenden Konzepts und vieles mehr.

Manfreds Blog

Written self-reflection is very powerful and - at the same time - it is still quite rarely used in the business context. Cosima talks with Lisa about why this is the case and what can be done to improve the situation.

Link

Organisation und communication have a huge impact on software desgin and architecture. Avraham Poupko and Kenny Baas-Schwegler take this a step further and talk about the influence of culture on software design.

Links

Book: The Corporate Tribe: Organizational lessons from anthropology

Book: Team Topologies: Organizing Business and Technology Teams for

Code is read more often than written. Felienne Hermans talks about how to read complex code with Lisa Moritz and the book she wrote about this topic.

Links

• Get 35% discount on Felienne’s ebook “The Programmer’s Brain” at Manning with the code podsoftarktv21

James Lewis is one of the microservices pioneers. We talk about when to use microservices and the organizational side of microservices e.g. the inverse Conway maneuver. Lately, James became interested in flow.

Links

Software architecture is fundamentally about how to split a software system into multiple parts. In this episode, we discuss this basic challenge: We talk about modularization with approaches like microservices and monoliths with Chris Richardson. Chris is a Java Champion and a Java One rock star. Nowadays, he works on microservices with his web site microservices.io and his book “Microservices Patterns”.

Links

Software architects are faced with uncertainty more often than we like to admit. How can we deal with it - or can we even make it disappear? In this episode, we will talk about uncertainty with Kevlin Henney. He has been a member of the IEEE Software Advisory Board, coauthor of several books on patterns, editor of 97 Things Every Programmer Should Know, and co-editor 97 Things Every Java Programmer Should Know.

Links