Skip to content
View original post on X: Santiago
Published
16/100

Santiago argues agentic coding's rollout and rollback problems grow with each feature

AISantiago (@svpino) says the more code agentic coding produces, the harder it becomes to keep applications from breaking for users. He lists four needs for each new feature: how to measure it, who gets it first, when to expand access, and a rollback strategy.
SantiagoVerified on X
@svpino
View on X

Here is a big problem with agentic coding:

The more code you write, the more complex it is to keep the application from blowing up in users' faces.

For every new feature you implement:

  • You need to determine how to measure it
  • You need to plan who gets it first
  • You need to decide when to let more people use it
  • You need a rollback strategy for when things go wrong

This is a huge problem, but we can fix this very easily! ↓

Source details

Santiago · x.comPublished · added here

Original title: Here is a big problem with agentic coding: