#automation
Every post tagged "automation".
36 posts · showing 21–30
-
Autonomous Refactors: What Makes One Safe Enough to Merge
Refactoring is what agents do best and what most easily produces an unreviewable disaster — for the same reason. One property separates the two, and it isn't how hard the change looks.
-
Requirements Are the Bottleneck an SDLC Agent Can't Remove
Compress implementation to nothing and delivery barely moves, because implementation was never the long row in the table. The constraint is upstream, it's organizational, and no tooling touches it.
-
The Ticket-to-PR Agent: Which Half of the Job It Does Well
The split wasn't by difficulty — some intricate tickets went fine and some trivial ones went badly. One question predicts it, and acting on it improves something other than your agent.
-
What "End-to-End Development Agent" Actually Means Right Now
The phrase covers demos that differ by orders of magnitude. Naming the eight stages shows which two are genuinely autonomous — and why chaining them is qualitatively harder than any one of them.
-
What Actually Got Automated Away in Previous Software Waves
"Automation always creates more jobs" is too coarse to use. What each previous wave specifically removed — and what it left — is a much sharper predictor, and this wave's profile mostly matches.
-
Cheaper Software Means More Software: The Demand Argument
Every previous drop in the cost of building software increased the number of builders. The mechanism is real and depends on one condition — which you can check in your own organization's backlog.
-
The Inbox Agent That Filed Everything Correctly and Lost Two Questions
Every filing decision was defensible, and two unanswered questions still vanished into the archive. The bug wasn't the prompt — it was that the agent judged messages while acting on conversations.
-
Computer Use: When the Agent Drives a Whole Desktop
Clicking is easy; knowing what to click is a perception problem solved from a screenshot. The failures are modals, focus loss, and scroll state — and an agent that assumes its click landed compounds errors silently.
-
Running Agents on a Schedule: What Changes Without a User
An agent someone triggers has a safety property nobody designs for: a person is watching. Put it on a schedule and that goes away — along with the feedback loop that was catching the errors.
-
The QA Agent That Wrote Tests That Always Passed
Coverage climbed, the build stayed green, and a real regression sailed through. An agent asked for passing tests writes passing tests — and the easiest passing test verifies nothing.