The ongoing debate over where AI coding agents belong, in an integrated development environment (IDE) or at the command line The post CLI or IDE? Build in verification first. appeared first on The New Stack.
The ongoing debate over where AI coding agents belong, in an integrated development environment (IDE) or at the command line The post CLI or IDE? Build in verification first. appeared first on The New Stack.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: The New Stack
- Published: 25/08/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
When a tool appears promising faster development, the useful question is not how much code it generates but how much work it generates downstream. Tests, review, security, technical debt, incidents: that is where the promise gets paid or charged.
I look at it from operations, not from the demo. The question is not whether the assistant writes a correct function, but whether the team can maintain what it produced six months later, with different people, without the original context. That is the real test and it almost never appears in the announcements.
What usually goes wrong
What usually goes wrong is that review does not grow at the same rate as production. The team generates twice as much and still has the same two people reviewing, who get tired, start approving faster, and three months later quality has dropped without any indicator showing it yet.
What to watch
- The effect on people newly joining the team, which is where judgement erodes fastest.
- Whether total time to production drops or only writing time, which is not the same thing.
- What happens to code review: if the assistant produces more, somebody has to read more.
How I read this entry
If I were rolling this out, I would do it with written rules: what can be generated, what always gets human eyes, and what is off limits to an assistant — typically anything handling money, identity or personal data. Rules give freedom, they do not remove it.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
