The false binary is “use AI” versus “be a real programmer.”
Orchid’s “Programming is art” makes a useful distinction from lived preference: the author likes building startups more than writing code, while some programmers value the act of coding itself and would keep doing it even if automation became dramatically faster.[1] That is an essay, not a census. But it names the category error cleanly.
Automation optimizes an outcome. Craft can include the route. A guitarist is not waiting for a faster way to produce an MP3; a programmer tracing a weird state machine may not be waiting for a faster way to receive a patch. Neither posture is morally superior. They are different jobs-to-be-done wearing the same IDE.
If the process teaches, delights, or forms your taste, “time saved” is not the whole scoreboard.
The clutch moved because the machine got a drivetrain.
VS Code 1.136 makes the shift concrete. Its preview Agent Merge feature can ask an agent to address review feedback, failed checks, merge conflicts, and workflow reruns repeatedly until a pull request is ready to merge.[2] The same release organizes delegated chats into parent-child session trees, with status and pending approvals visible per chat. That is not autocomplete with a bigger text box. It is work orchestration.
The accompanying Agent Host architecture post goes deeper: a dedicated process owns sessions across windows, while different harnesses keep their own loops and capabilities behind a shared, actively developing protocol.[3] When the runtime can persist beyond the window, the human craft migrates toward framing, constraints, observation, review, and deciding when the loop has actually earned trust.
Delegation is not disappearance.
Cursor’s September 2 self-hosted machines update says tool execution can stay on internal infrastructure while agents handle tool calls locally. It also describes team worker pools, idle-machine hibernation, execution on third-party sandbox infrastructure, and computer use on Linux and Mac.[4] Those are vendor claims about a product surface—not proof that every setup is safe or economical.
What matters here is the shape: the person is no longer only choosing lines. They may be choosing the worker pool, network boundary, machine image, task contract, evidence, and takeover point. That can be excellent engineering craft. It can also become managerial pantomime if nobody understands the generated system.
Use four gears, not one culture war.
- Hand. Keep the process manual when the process itself is the value.
- Pair. Ask for alternatives, explanations, tests, and critique while retaining authorship.
- Delegate. Hand off a bounded outcome with explicit constraints and evidence.
- Loop. Permit autonomous repair only with a stop condition, inspectable receipts, and a named takeover path.
The right gear can change by task. Hand-write the parser because you want to understand it. Delegate the migration because the contract is boring and sharp. Pair on unfamiliar code. Let a loop grind on mechanical review fixes. Craft is not a fixed percentage of keystrokes; it is deliberate control over what you refuse to make invisible.