Tag: ai
All the articles with the tag "ai".
The Reply Arrived Twice. The Record Updated Once.
Inbound replies and webhooks must link to the right record exactly once, and generated drafts must wait for a human. Two mechanisms from production systems: key on the sender id, hold behind a gate.
The Code Changed. The Description Had to Survive It.
Code changes flow back into the knowledge graph the generator reads: changed files only, merge not replace, both artifacts patched. Freshness as write back, not retrieval ranking.
The Test Passed. The Agent Never Called the Tool.
Grading an agent on the artifact it produced tells you nothing about how it got there, which is the one thing a tool-use environment exists to measure.
I Wrote the Tool for a Human. An Agent Called It.
An agent has only your response bytes to reason from, which turns error messages into control flow and makes response size a correctness property.
Nobody Typed the 10,000 Lines. The Review Belonged Upstream.
In a generated system the unit of review is not the output, it is the template that emitted it, because a defect there ships in every instance at once.
The Model Wrote the Code. The Build Gate Was the Product.
An AI code generator that must compile and run its own output before it delivers, and the exit conditions that keep the loop from hanging.
The Webhook Must Reply in Seconds. The Useful Work Takes Longer.
Designing a Go alerting service where every operation worth doing is slower than the budget you have to respond in, and the sender retries if you are late.