Welcome to the digest #2 of my “Technical Leadership and Architecture insights” (or TLA_insights for short).


Although this is just iteration #2, I am already pivoting the format a lot 😄 (learn fast and make it better). The following changes were made:

I hope you appreciate these changes, I am really excited about them as it allows more regular and interesting insights to be published and also create a clearer knowledge base of insights. I have a few other ideas in mind that I will be working on moving forward, so stay tuned!

On a personal note: September and October were very eventful in terms of developments on topics relevant to TLA_insights:

I hope you have fun and find some interesting insights here. Don’t hesitate to contact me via email or on Twitter me if you have questions or want to chat about these topics.

TLA_insights digest #2

light Team Topologies, Matthew Skelton & Manuel Pais

Insights on the book Team Topologies, a book that brings a lot of interesting new ideas on how to approach organization / team design and its "evolution" from a "team first strategy" and "team cognitive load" perspective. The book presents clear motivation for this strategy and then proposes 4 basic team topologies and 3 types of team interaction modes to approach such org design and evolution.

“To me, Team Topologies is becoming a reference book to help on the design and evolution of organizations and their sociotechnical architecture!”

🔗 full-text

light Secrets of a Strong Engineering Culture, Patrick Kua

Great presentation by Patrick Kua on "secrets" of Strong Engineering cultures, i.e.: things to cater for in order to have an organization that moves at high-velocity, but also is a great place to work, where people feel motivated and can thrive in their activities. By having such traits, organizations also have higher changes of attracting and retaining great talent - a big challenge in our current market.

Building great engineering cultures is not trivial: they take time to build, they are not “projects” with a due date but are a continuum, an infinite cycle of improvements. Make this explicit and make the core elements of your culture visible so people can see it and know how to contribute to it and improvement it.

🔗 full-text

light Software Architecture, Team Topologies and Platforms, Matthew Skelton & Manuel Pais

In this podcast Manuel Pais and Matthew Skelton talk about several elements of Software Architecture and traits of modern Software Architects - many well positioned on their book Team Topologies. I couldn't agree more with the core remark of the conversation, which I summarize as: the Modern Software Architect is a Sociotechnical Architect.

Modern Software Architects cannot anymore purely focus on the Technical systems anymore. They must be “Sociotechnical Architects”: be able to consider the organizational and technical systems in the problem & solution spaces. Ignoring this is recipe for partial optimizations and in most cases a lot of “synchronization overhead and waste”.

🔗 full-text