Estimation: Why It Fails and What Works Better
Why software estimates are systematically wrong in the same direction, and the practices that produce more useful forecasts than a single number ever could.
Tag
11 articles
Why software estimates are systematically wrong in the same direction, and the practices that produce more useful forecasts than a single number ever could.
How Amazon's two-pizza teams, operational readiness reviews, and correction-of-error documents work together as an operating system, not just slogans.
Why undocumented architectural decisions get relitigated endlessly, and how a lightweight ADR practice preserves the reasoning without becoming bureaucratic.
A practical framework for the first 90 days on a new engineering team, from mapping the codebase to earning trust before shipping big changes.
How trunk-based development and merge queues reduce integration pain compared to long-lived feature branches, and what they require to work in practice.
Why most postmortems produce a document nobody acts on, and what separates a blameless postmortem process that genuinely prevents repeat incidents.
How to write code review comments that engineers actually act on, without triggering defensiveness or turning review into a status contest.
Why Spotify organized engineering around autonomous squads instead of functional teams, and what the model got right and wrong as the company scaled.
Design docs stall for predictable reasons — missing context, buried trade-offs, no clear ask — and each one has a specific, fixable cause.
Mentorship advice usually addresses only one side of the relationship — the skills that make it work are different depending on which seat you're in.
Seniority shows up less in what someone knows and more in a handful of repeatable habits around scope, communication, and how they handle being wrong.