Leave Architecture Review With a Decision, Not Homework
A review board earns its place by what leaves the room, not by what it approves. Three seats, four questions, four legal endings and the rules for writing advice back.
Tag archive
A review board earns its place by what leaves the room, not by what it approves. Three seats, four questions, four legal endings and the rules for writing advice back.
Most companies do not start their platform journey with a platform team. They start with a collection...

Why I think a technical lead should keep shipping small, real changes, what that looks like, and where the view stops applying.

How leaders build a blameless postmortem culture: what a postmortem is, when to write one, a template, how to run the review, and the leadership behaviours that make teams tell the truth.

AI tools write the small changes that taught engineers the craft. What I think that changes about how juniors grow, and what I am still unsure of.

Quick Answer t-shaped goals for frontend vs backend engineers: Explore how t-shaped goals...

Developer productivity cannot be measured with one number. The five SPACE dimensions, metrics to use for each, how to combine surveys and system data, and the mistakes that destroy trust.

Technical debt explained for leaders: the four kinds of debt, how to measure its “interest”, a scoring model to prioritise it, how much capacity to fund, and how to talk about it with the board.

How to organise engineering teams from 10 to 100+ engineers: the four Team Topologies team types, three interaction modes, the signs your structure is failing, and a step-by-step reorganisation plan.

Why I think a one-on-one should never be a status update, what it is for instead, and where that view stops being true.
Murthy had already seen a startup fail. His company Softronics folded after about a year and a half,...
How to measure where AI nets you time and where it adds hidden work to your team A team lead tells...