Author

Powerduck

3 min read

The agent drifts from your requirement while the context fills up

You asked for one behavior; twelve tool calls later it optimized the last output instead of the acceptance criteria. Context fills with intermediate logs, recent tokens dominate, and the original brief gets buried. Here is how drift happens and the cheap anchors that keep a task on rail.

Read article
4 min read

The agent wrapped everything in try/catch and your errors disappeared

Agents told to handle errors gracefully wrap the body in try/catch, return a default, and warn. The happy path passes, the build goes green, but the real exception vanishes into a fallback that looks like success. Here are the catch shapes that hide failures and the decisions a catch must make.

Read article
3 min read

The AI test that passes because it copied the code's assumption

An agent writes the implementation and test in one pass, and the test repeats the assumption the code made. Wrong the same way, so green proves nothing. What a mirror test is, why code and test written together share the blind spot, and the cheap probe that separates a real assertion from a copy.

Read article
2 min read

An agent ships the forward migration and forgets the way back

The forward migration applies cleanly, but the PR omits rollback, old-row backfill, and a read-after-write check. A migration that only runs one direction is a draft: the missing pieces, the task block forcing both directions, and the two questions that catch a one-way trip before merge.

Read article
2 min read

An agent PR that only says 'fixed' makes the reviewer redo the diagnosis

An agent that reports 'done, tests pass' leaves the reviewer to redo the diagnosis. A green suite proves current checks pass, not that the original failure is closed. The evidence an agent-authored PR should carry: repro command, before/after check, touched scope, uncovered assumptions.

Read article
4 min read

Postman vs Bruno vs a local-first OpenAPI studio: choose by where the spec lives

Postman, Bruno, and a local-first OpenAPI studio optimize a different assumption about where the API contract lives: a cloud collection, plain files in git, or the spec itself. The right choice follows that assumption, not UI polish. Here are the honest tradeoffs and a short decision checklist.

Read article