#coding-agents
Every post tagged "coding-agents".
49 posts · showing 21–30
-
Staying Employable When Code Generation Is Nearly Free
"Develop judgment, move up the stack" is true and unactionable. Six specific moves instead — and the hedge and the bet turn out to be the same actions.
-
Will Open-Source Harnesses Eat Commercial Coding Tools?
The premise is right — the loop is a few hundred lines. The conclusion is too fast, because the loop isn't the product, and one of the real advantages is invisible from outside.
-
IDE Assistants vs Agent Harnesses: Different Products, Different Futures
They get discussed as one category and have opposite requirements on latency, context, failure cost, and model tier. One is commoditizing into a feature; the other's differentiators aren't AI capabilities at all.
-
The Compounding Loop: Agents Building Agent Infrastructure
Agents are good at building the harness that makes agents useful — well-specified, verifiable plumbing. The loop is real, and it has a hard boundary at everything requiring judgment about what to build.
-
Debugging Code You Didn't Write and Don't Understand
The instinct is to hand the failure back to the agent. Without a reproduction that produces a plausible fix to a plausible cause — and two rounds later nobody understands the module at all.
-
Novel Problems vs Recombined Ones: The Line That Matters
On genuinely novel problems you don't get an error — you get the nearest known pattern applied confidently to an adjacent problem. One classification decides where your attention belongs.
-
When the Requirement Itself Is Wrong, Who Notices?
The behavior was intentional, decided two years ago, documented somewhere nobody looked. Every stage faithfully executed a wrong ticket — and every automated check confirmed it, by construction.
-
The SDLC Steps That Resist Automation Longest, and Why
Order the lifecycle by automatability and it doesn't track difficulty at all. Two properties decide it — and the steps that resist are short, frequent, and where all the leverage sits.
-
What an Agent-Run Sprint Actually Looks Like
Not the same sprint faster — an inversion. Most of the week becomes specifying and reviewing, review becomes the constraint, and integration becomes the new time sink.
-
Code Review When Most Code Is Agent-Written
Review practices assumed an author who had reasons, understood the system, and made idiosyncratic mistakes. Agent output breaks all three — and the bugs that survive are the ones that look correct.