From 2022 Dev to Now: The Job Changed While We Were Typing

In 2022 the future arrived as a grey ghost in the editor. Copilot offered the next line. You accepted or you did not. The rest of the job was still the job: Jira, Slack, a browser full of docs, a PR that a human wrote in the shape of a human day. Hours in the IDE meant hours of intent. Stack Overflow was a place. Certainty was still a feeling you could earn by typing.

That world did not explode. It thinned. By 2024 the chat window had opinions about architecture. By 2025 the agent could plan, patch, run tests, and open the PR while you were in another meeting. The 2022 developer was a person who wrote software. The 2026 developer is a person who directs, constrains, and is blamed for software that a system produced at a speed no stand-up was designed for.

January to August of this year is the chapter you cannot unsee. Agent mode stopped being a novelty sidebar and became the default in the tools people actually pay for. Cloud agents in isolated machines. Sub-agents in parallel. Model routing as a skill: this brain plans, that one executes, a third one reviews so you do not grade your own homework. Token cost showed up as a line item next to AWS. Review time overtook write time. Studies argued experienced people could feel faster and measure slower. The industry did what it always does with a paradox: it bought more seats.

The week changed shape. Monday is a contract — outcomes, non-goals, the thing that must not happen. Tuesday is a swarm of diffs. Wednesday is the seams: Clerk, Stripe, a migration, the Expo client on a bad network. Thursday is proving the agent's story against production's. Friday is explaining to someone with a budget why "the model finished" is not a release.

What we lost: the private pride of a function only you could have shaped. The long afternoon of not knowing, which used to be how seniors were made. Some of that loss is grief. Some of it is the tax for not drowning in boilerplate.

What we gained is leverage that used to require a department — and a threat model that used to require a specialist in the room from day one. Security is not a later phase when the machine can widen IAM in a polite paragraph. Hardware is not furniture when the laptop is an inference budget. Metrics that counted hours and lines look like folklore.

If you learned to develop in 2022, you do not need to throw the craft away. You need to relocate it. Syntax is cheap. Taste, verification, and the courage to refuse a fluent wrong answer are the job. The typing was never the point. We only notice now because something else is doing it.

From January through August the calendar was not a list of product launches. It was a sequence of defaults flipping: agents in the cloud, parallel workers, review as the main verb, security incidents that treated the developer machine as the prize. If you only read changelog tweets you missed the plot. The plot is that the 2022 loop — type, search, stack overflow, PR — got replaced by intent, generate, interrogate, merge, and you are still responsible for the last word.

Bring the 2022 crafts with you. Debugging. Naming. Knowing when the network is the bug. They did not become obsolete. They became the way you catch a fluent liar.

The job changed while we were typing. Look up. The cursor is still blinking. It is waiting for a decision, not a character.