Field notes on code, debt and judgment in the LLM era.
Essays from the team behind CodeNSM — first a long, honest walk through the problems of the AI coding era, then the methodology we built in response: what production telemetry reveals about codebases, why the old debt instruments stopped working, and how we run pre-registered science on the results.
The Problem — a 30-part walk through the AI coding era
Written to be read in order. Start at Part 1 →
The Standup — thirty parts on the one meeting still run from memory
The brief nobody wrote: how standup prep turns into ritual
Someone invented your standup on purpose, to solve a real problem. Eighteen months later it's a recitation nobody remembers agreeing to. A grounded-theory study that sat through 79 real standups found the exact moment the meeting stops being a meeting.
The Standup · Part 2Never ask what the system already knows
"Which services are hot right now?" is a question with an answer sitting in a dashboard nobody opened. Every time a standup asks it out loud, it's charging the team a tax for information the room already owns. There's a fifty-year-old consulting principle for designing questions that don't do that.
The Standup · Part 3"I understand the retry logic": the illusion that ends careers quietly
Ask someone to explain how a zipper works and watch their confidence collapse mid-sentence. It's the same mechanism sitting under the most dangerous four words in any standup: "I understand this." A 2002 psychology paper mapped exactly how the illusion forms, and it has nothing to do with how the sentence sounds.
The Standup · Part 4A reference class of one: why "by Thursday" is a genre of fiction
Every estimate in your standup is a work of fiction written in the optimistic-realist genre, and the person writing it has no idea they're doing it. Kahneman and Tversky named the bias in 1979. A Danish economist turned it into a forecasting method used on billion-dollar tunnels. Neither of them worked in software, and both of them explain your sprint.
The Standup · Part 5The thing nobody said out loud
Put five people in a room, give each of them one piece of unique information and a pile of shared information, and watch the group talk almost entirely about the pile everyone already had. This isn't a personality flaw. It's a forty-year-old, heavily replicated finding about what groups are structurally bad at — and it happens in your standup on a schedule.
The Standup · Part 6Your bus factor has a name, and it's measurable, not folklore
Every team jokes about the bus factor and no team measures it. There's an actual algorithm for computing it from a commit graph, and a separate Microsoft Research study showing that low-ownership code ships measurably more defects. Put them together and "I'm the only one who really knows this" stops being a joke someone tells in standup and starts being a number.
The Standup · Part 7The question telemetry cannot answer
Your monitoring stack can tell you charge() failed nine times last hour. It cannot tell you what that actually cost you — in refunds, in trust, in the one customer who never came back. There's a fifty-year-old philosophical argument for why no dashboard will ever answer that question, and it doubles as the design spec for the only question worth asking a human out loud.
The Standup · Part 8Context has a half-life, and a confident stale answer is worse than none
The fact you learned about a system six months ago is not the same fact today, even if nobody told you it changed. Memory research mapped exactly how fast this happens in a single brain in 1885. Organizational research mapped the same decay across whole companies more than a century later. Neither of them thinks a stale, confident answer is better than admitting you don't know.
The Standup · Part 9The agenda is the call graph, not the seating chart
Your standup goes around the room in the order people happen to sit, or the order they happen to report to someone. Your codebase doesn't care about either. A 1968 essay everyone's heard of and a 2008 study almost nobody has explain why running the meeting in dependency order — not org-chart order — is the difference between coordination and a very expensive round of show and tell.
The Standup · Part 10The premortem that fits in a standup
Imagining a project has already failed, in detail, before it starts, sounds morbid and turns out to work — 30% better, in the original lab result. Gary Klein compressed it into a boardroom exercise. It fits in a standup in one sentence. This closes the arc: everything before the room, ending in the one question that turns dread into a claim you can actually check.
The Standup · Part 11A standup is a prediction market (that nobody is running)
Every 'I'll have it done by Thursday' is a forecast about a world that doesn't exist yet. Wall Street built an entire industry around scoring forecasts like that. Your engineering org built a calendar invite.
The Standup · Part 12Keep the sentence: why paraphrase is where accountability goes to die
Somebody says something in a standup. By the time it matters, what gets remembered is a tidy summary — and the summary is never neutral. It is quietly, invisibly, edited by whoever wrote it down.
The Standup · Part 13Sixty-one percent of this meeting cannot be checked
Not every sentence in a standup is a lie. Most of them are worse than a lie: they're not even wrong, because there's nothing in them a fact could disagree with. That's a real number, and it might be the most useful one your team has never seen.
The Standup · Part 14Watermelon status: green outside, red inside
Every project manager has a name for the status report that says 'on track' right up until the week it explodes. The report wasn't wrong by accident. Somewhere between the code and the calendar invite, somebody made a very human, very predictable decision not to say the quiet part.
The Standup · Part 15The blocker that was never a blocker
'Still blocked on the staging DB' is the most restful sentence in software. It sounds like an update. It has been the same sentence for eleven days. Nobody is timing it, which is exactly why it can keep being the same sentence.
The Standup · Part 16Talking time is not signal
There's a famous study that supposedly proves quiet people are secretly the smart ones. It doesn't say that. It says something narrower, stranger, and much more useful — and almost nobody who cites it has read past the abstract.
The Standup · Part 17You think they heard you. They didn't.
You said the sentence. It made perfect sense in your head, which is exactly the problem: your head is the only place it fully existed. Two well-documented biases explain why you'll walk out of every standup overestimating how much you actually communicated.
The Standup · Part 18'Yeah, got it' is not evidence of anything
Two people nod, say 'got it,' and move on, both privately picturing a different version of what was just agreed. This isn't a rare failure of attention. It is, by design, the cheapest way two minds can end a conversation — and cheap is not the same as true.
The Standup · Part 19Safe to be wrong
A falsifiable claim is a small act of courage: it hands the room a way to prove you wrong. Teams that punish being wrong don't get fewer mistakes. They get better hedging — which means every idea in this series depends on a precondition almost nobody names out loud.
The Standup · Part 20The decision nobody recorded
'We're dropping the Redis cache' takes four seconds to say in a standup and can take four months to re-litigate, in full, by people who weren't in the room the first time. A decision without a record isn't a decision. It's a rumor with a deadline.
The Standup · Part 21Calibration, not confidence: the only score that has ever mattered
Two forecasters, same city. One says '70% chance of rain' and is right about 70% of the time. The other says 'DEFINITELY' and is right about half. You'd trust the first one with your wedding. You run your engineering org on the second one, every single day.
The Standup · Part 22Two of two is not one hundred percent
A round number is the most seductive shape a statistic can take, and small samples hand them out for free. Why '100% calibrated' from two resolved claims isn't a compliment — it's a warning label nobody printed, and Laplace worked out the fix two hundred years ago.
The Standup · Part 23You always knew it would break (you just never said so out loud)
The outage retro has a ritual: someone says 'honestly, I had a bad feeling about that module for weeks.' Fischhoff proved, in 1975, that this is almost never a memory. It's a manufacture — and an unrecorded prediction is worth exactly nothing at the retro.
The Standup · Part 24Did the commit agree? What 'done' means when a human and a repository disagree
Thursday standup: 'yep, that fix is done.' Everyone nods. Nobody opens the repository, because checking would feel like an accusation. What actually made that sentence true — the code, or the sentence?
The Standup · Part 25Production is the referee: a claim about 'why' isn't settled by who's most senior
Someone senior says, with total conviction, 'the flakiness is the retry logic, not the queue.' Nobody argues, because arguing with the most senior person in the room about a technical call is a bad career move. Ronny Kohavi has a name for this, and a decade of data on how often it's wrong.
The Standup · Part 26Unresolvable is a finding: why 'we don't know yet' has to stay on the scoreboard
A claim nobody checked isn't 'probably fine' and it isn't 'probably wrong' either. Medicine had to learn this the hard way in 1995. A standup has the exact same failure mode, and folding it away is a worse kind of dishonest than being wrong.
The Standup · Part 27The day velocity became a target (and stopped being a measure)
Goodhart wrote about UK monetary policy in 1975. Campbell wrote about social indicators in 1979, from an entirely different tradition. Strathern gave the whole thing its famous one-liner in 1997 — about auditing universities. Almost everyone quoting 'Goodhart's Law' is actually quoting Strathern.
The Standup · Part 28Blameless, and still scored: where the line actually has to sit
A system that checks what people said against what happened, per person, is one short step from a surveillance system that scores humans. This post doesn't dodge that. It argues, specifically, why it isn't the same thing — and states the bright lines that would make it become one.
The Standup · Part 29The quiet engineer was right
Four sentences in a half-hour standup, right more often than the person who dominated the room. Research on trait dominance and 'the babble hypothesis' explains why nobody noticed — the room was never measuring what it thought it was measuring.
The Standup · Part 30What the sprint actually bought
Seventeen tickets closed, a clean burndown, confetti in Slack. Ask the room whether any of it landed on the code the business says it depends on, and watch the silence. The closing part of this arc points thirty parts of argument at the sprint itself.