About
Fifty notes on developer productivity engineering, written from the operator's side.
Who this is for
Whoever owns the toolchain and needs evidence to prioritise. Team leads seeing the symptoms without a name for the cause. Platform teams defending time for systemic work. Anyone who has been handed a slow build and a deadline.
How the notes are written
The mechanism before the product. What caching, selection and incremental builds actually do, and where each fails, before any question of tooling.
Methods you can run. Where a note says something is measurable, it says how, usually from data your CI system already holds.
Limits stated plainly. One note is entirely about what this work cannot fix, and another is a list of requests to refuse.
The uncomfortable findings included. Most programmes produce dashboards and no change. Coverage as a target reliably produces tests that assert nothing. Adding runners can make execution slower. Build performance work eventually becomes architecture work, which is a much larger conversation than the one it was scoped for.
The boundary on measuring people
A measurement capability attracts requests for per-developer numbers. These notes argue against them and give the reasons: they measure the environment rather than the person, they are trivially gamed, they punish review and mentoring and debugging, and — most practically — they degrade the data the programme depends on, because developers who believe the telemetry is aimed at them will disable it.
DORA and SPACE are both cited in support of individual measurement and both warn against it explicitly. These notes read them as written.
Editorial position
No vendor material, no sponsored content, no affiliate arrangements, no product rankings. Where tooling is discussed it is in terms of what to test on your own codebase and what to ask.
No benchmarks are quoted. Comparable figures depend on too much context, and published ones are self-selected.
About this domain
This address previously belonged to a long-running book review blog, written by a named individual and containing guest posts and interviews by many others.
None of that material is here and none of it should be. Beyond the blogger's own writing, the site carried work by dozens of authors, publisher cover images, and giveaway entries containing personal data. Acquiring a lapsed domain transfers rights to none of it, and no single permission could cover it.
Every previous address returns a clear "gone" response rather than redirecting to unrelated material.