#automation
Every post tagged "automation".
9 posts · showing 1–9
-
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.
-
The Documentation Agent That Actually Kept Docs in Sync
Ask an agent "do the docs need updating?" on every PR and you get noise reviewers close unread. Trigger on contract changes, forbid new prose, cite the source line — and run the corpus-wide contradiction check first.
-
The Migration Agent: 4,000 Files and What Made It Tractable
The difference between a migration agent that saves weeks and one that produces four thousand unreviewable diffs is decided before it touches a file — and it starts with building the checker, not the agent.
-
The Code-Review Agent That Commented on Everything
Nine comments on a twelve-line PR and the team muted it. Any agent asked to find things will find them — the fix is a hard cap that forces ranking, and pointing it at what humans actually miss.
-
The Data-Cleaning Agent and the Column It Silently Dropped
It normalized the phone numbers, standardized the country codes, and quietly deleted 412 rows that looked untidy. Any task phrased as "make this better" reads as permission to remove what doesn't fit.
-
Chatbot, Workflow, or Agent? Pick the Simplest Thing That Works
Six weeks building an agent for a task with three fixed steps. One question — can you draw the flowchart before seeing the input? — separates the three architectures and saves most of that time.
-
The Triage Agent That Should Have Been a Filter
A routing agent replaced a set of rules and made the common case slower, pricier, and less predictable. The lesson isn't "don't use agents" — it's that judgment is worth paying for only where judgment is required.