Some Things I Read June 2022
A Taxonomy of Technical Debt
If you are going to focus on any technical debt, focus on the stuff that is contagious.
Getting Real about Managing up
Technically a video but you get the idea.
The key takeaway, your manager is not thinking about you so make their job easy.
How Do Committees Invent?
The classic paper that spawned Conways Law.
Organizations, who design systems, are constrained to produce designs which are copies of the communication structures of these organizations.
It is a very interesting read and made me start to think more about the nature of organisational design and it’s impact on software architecture.
We shall see in detail later that the very act of organising a design team means that certain design decisions have already been made, explicitly or otherwise. Given any design team organisation, there is a class of design alternatives which cannot be effectively pursued by such an organisation because the necessary communication paths do not exist. Therefore, there is no such thing as a design group which is both organised and unbiased.
Recommended by the ever brilliant Dennis Hotson. Essentially an extended rumination on Conways Law and how you can leverage that tendency to make better decisions on team structure.
The big takeaway for me at the moment is thinking about software teams more like you think about software: keeping dependencies loosely coupled, agreeing on contracts for communication etc.
The Art of the Tick Tock Doc
A good guide for structuring comms around big disruptive changes in large scale organisations. Communicating effectively is hard.
Less of something to read, but it was an interesting discovery for me that telephones exist which are powered by the mere act of talking into them.