I Automated the Work. The Work Moved.

Every.to published a look at its own operations this week, and one finding has been rattling around my head since: the more they automated, the more work landed back on humans. Not the same work — the producing got faster — but coordination, prioritization, and judgment calls piled up in its place. Automation gave them leverage, not elimination.

I run a small content pipeline of my own — n8n plus Claude, stitched together over a few weekends — and this matches my experience exactly. The pipeline drafts happily and endlessly. What it cannot do is decide what's worth saying, notice when a draft sounds like nobody in particular, or fix its own instructions when quality drifts. Since building it, I write less and review more. The hours didn't disappear; they changed shape, and honestly the new shape is harder. Judging is more tiring than typing.

If you manage a team, this reframe matters more than any individual tool announcement. Treating AI adoption as a headcount equation — "the model handles X, so we need fewer people for X" — consistently underestimates the coordination and decision-making overhead that grows in automation's shadow. The teams getting real value from tools like Claude Code aren't doing less work. They're doing different work, higher up: architecture, specs, and the constant question of whether the output is actually good.

The same pattern shows up in this week's security news, in a less comfortable form. JFrog's analysis of 18.2 billion artifacts found attackers increasingly going after AI development tools themselves, not just the code they produce. At the same time, vibe coding keeps pushing production-bound code past the reviews that would normally catch problems. So the attack surface is growing while the review surface shrinks. If automation moves human work up to the judgment layer, code review is precisely the judgment we can't skip — and it's the first thing teams are skipping.

A few smaller things from the week that I'd flag. C# 15 is getting native union types with .NET 11 — I've built enough verbose OneOf workarounds to be genuinely pleased, and it's nice evidence the language team listens. Anthropic published a detailed post on how they contain Claude across their products, and it's worth reading slowly even if you never touch an AI agent, because it's really about blast-radius thinking: least privilege, sandboxed execution, capabilities as deliberate grants. The same discipline that makes good microservices makes safe agents.

If you're adding automation to your own workflow this month, my suggestion is simple: before you build it, ask where the judgment goes afterwards. Something still has to decide whether the output is right, and that something is you. Plan your time for it — it's the part of the job that just got bigger.