Topic
Paste a stack trace, get a try/catch around the whole function. The error still happens — now it returns undefined and the caller has no idea. Wrapping a call is not handling a failure.
Read articleAn agent-generated PR description reads the diff and narrates it back. It never explains why the change was needed, what could break, or what the author actually worried about. That last part is the whole point of review.
Read articleA 4-hour agent conversation starts re-suggesting things it already tried. The fix isn't more prompting. It's a checkpoint and a clean session.
Read articleAn agent's claim of 'done' is worthless without a one-line command that proves it. The cheap discipline: no task closes until the agent leaves you something you can paste into a terminal.
Read articleDumping every file into the prompt doesn't give the agent more signal — it buries the one file it actually needs. The cheap fix is a file-level context manifest, not a bigger context window.
Read articleWhen a coding agent hits a flaky test at 2am, it doesn't stabilize the test — it lowers the assertion until the suite goes green. Here's what that actually costs you, and the cheap gate that catches it.
Read articleMost MCP servers load everything eagerly, dump huge schemas into the system prompt, and make the agent pay for tools it will never call. The fix is boring: lazy, narrow, and spec-driven.
Read articleAn AI review bot that reads a diff the AI itself wrote is the author reading their own essay out loud to a friend who already agrees. The only useful review comes from a signal the code didn't generate.
Read articleThe default move when an agent gets something wrong is to paste more files into the context. But more files means more noise, and noise is what made it wrong in the first place.
Read articleA clean architecture diagram can hide a broken transition. Trace one failure boundary, verify it in code, and turn it into an API scenario test.
Read articleA failing request needs its environment, caller, and starting state. Preserve those conditions when handing an API investigation to AI.
Read articleA create-read-check scenario connects an API contract, MCP tools, and observable outcomes. Here is how to make completion something you can verify.
Read article