#intermediate
Every post tagged "intermediate".
223 posts · showing 71–80
-
When to Stop Improving an Agent
There's always another failing case, so without a stopping rule the work either never ends or ends arbitrarily. The signal isn't the error rate — it's effort per point of improvement.
-
The Economics of an Agent-Heavy Team
Several line items move and only one of them is tokens. The savings are real, land on a single term, and are partly consumed by four others that grow — which is why big speedups produce modest delivery gains.
-
How to Run an Agent Pilot That Produces a Decision
Most pilots end without a decision because they were designed to produce a demo. Write the threshold before you build — and sort the failures by cause, because "no-go" and "fix one thing" look identical in the average.
-
Buying vs Building Agent Capability as a Company
Framed as a technology decision, which is why it goes wrong. One question settles it: if a competitor bought exactly what you're buying, would they have what you have?
-
The Documentation Problem Agents Create
Documentation has two audiences with different needs, and generated docs that restate the code become negative value the moment they drift — a confident wrong answer with an authoritative source attached.
-
Open Source After Cheap Contributions
Contribution effort rationed demand for maintainer attention. That rationing is gone and the attention is unchanged — but the filters that work test for something effort was only ever a proxy for.
-
Security Review When Nobody Wrote the Code
Human vulnerabilities carry a tell — hurried code, an obvious shortcut. Generated code is uniformly careful-looking, so scanning for the suspicious part stops working. But its consistency cuts both ways.
-
Why Your Codebase Will Grow Faster Than Your Understanding
Writing code built understanding as a byproduct, which is why "the team knows the system" used to be true without anyone planning it. That coupling broke and only one of the two rates changed.
-
Technical Debt in the Age of Cheap Code
The old rules assumed writing code was the expensive part. When it isn't, imperfect implementations matter less and surplus surface matters more — and the create-versus-remove asymmetry gets worse.
-
Onboarding Into a Codebase Nobody Fully Read
"Ask whoever wrote it" assumed someone did. Where code arrived complete in one commit and was approved rather than authored, the history holds no reasoning — and onboarding is where you find that out.