Posts tagged Agentic Coding — AI × software engineering, made practical.
You'll learn why juniors who review agent-written code without ever struggling through it themselves fail to build real engineering judgment, and how to reintroduce that struggle on purpose.
A worked example that turns 'cost per task' from a vendor invoice into the number your FinOps partner actually needs — plus the one-line PR template change that gets you there this sprint.
The hallucination that actually burns engineering teams isn't a wrong answer, it's a confident 'tests pass' with no test behind it — here's why that failure mode has no name yet and no fix except one you build yourself.
The router flip that saves you at the app layer is the same router flip that can quietly wreck you at the data layer — here's the exact mechanism, and the three-phase pattern that closes the gap.
Same class of agent mistake, same clean-looking diff, two identical-looking review processes — but only one team's safety net was actually built for a world where nobody's watching the code get written.
Your coding agent's vector store isn't broken — it's answering with code that stopped being true weeks ago, and nothing in the UI will tell you which answers to trust.
An agent invented one plausible status string, it sailed through review in 90 seconds, and three days later it was quietly erasing money from a finance report — here's the schema fix that makes that kind of guess impossible to write.
A green build in an agentic loop can mean the code is correct, or it can mean the loop simply agrees with itself — here's the exact commit where an agent proved the difference the hard way.
The agent's PR reads clean, tested, and confident, which is exactly why you stopped actually checking it — and that quiet swap is more dangerous than the review everyone knew got skipped.
Four reviewers went silent on a technically-better refactor because it answered the wrong question — and once you see why, you'll never let an AI agent near a vague ticket again.
A ninety-second permission review, one YAML line, and the moment I realized directory-level access control was built for humans who own the incident — not agents that only own the ticket.
When agents start merging their own PRs, deploy frequency stops measuring speed and starts hiding the one number that actually protects your users.
Agents didn't make PhoenixDX slower on purpose — they just moved the traffic jam from the keyboard to the review queue, and almost nobody measures that second line.
Agentic tools didn't remove your team's bottleneck, they relocated it into review — and if you're still counting lines shipped instead of diffs someone can actually vouch for, you won't see the damage until it's the root cause in your next postmortem.
A stale wiki link, a blank rollback field, an unwritten team assumption — any one of them is enough to sink an agentic coding run, because for that run, it's the entire dataset.
That confident, plausible, wrong edit your agent just made wasn't a hallucination — it was a stale cache hit, and every long agentic session has the exact same one sitting inside it unmonitored.