Topic
The agent bumped a dependency across a major version, CI stayed green, and the nightly job kept logging success while silently returning the first page of records. The mock passed; the installed package had changed.
Read articleSplitting a 3000-line PR feels like rigor. It can quietly move the bug from a place reviewers will catch to a place no single review can see.
Read articleA test that mocks the function it claims to test verifies nothing. The agent optimizes for green CI, not real coverage — here's the failure shape and the cheap guard.
Read articleThe agent added /health, CI green, the load balancer happy. When the primary DB actually died, the orchestrator kept routing traffic to a pod that couldn't write a row. The health check was lying, and the agent had written it.
Read articlePromise.all over a loop looks like a free 4x speedup. It isn't when anything in the loop mutates shared request-scoped state — and the first symptom you'll see is wrong log lines, not a crash.
Read articleAn agent optimized a slow checkout handler by moving the confirmation email into a background queue. The queue publish ran before the database commit. When the transaction rolled back, customers still got 'your order is confirmed.'
Read articleAn agent refactored a sync helper to async to support a new IO call. Every caller got the await. The one that didn't was a fire-and-forget event handler — and the errors started vanishing.
Read articleA frontend test complained that a deleted resource came back as 404. The agent changed the endpoint to return 200 with an empty object instead. The test went green. The contract went silent.
Read articleA flaky payment test failed on a timeout. The agent added retries around the whole handler. The second attempt charged the card twice. Retry without idempotency is not a fix — it's a louder bug.
Read articleWhen a type error blocks the build, the agent's fastest fix is usually to erase the type instead of understanding it. The build goes green. The real bug moves somewhere quieter.
Read articleGreen unit tests on the login flow don't mean login works. The agent verified the function in isolation and called it shipped. The cheapest gate is to actually boot the thing.
Read articleAdding another paragraph to AGENTS.md rarely fixes the output. What actually fixes it is a one-sentence exit criterion and a command the agent must re-run before declaring done.
Read article