I've watched two cohorts at my company. Cohort A treats Copilot/Claude Code as autocomplete on steroids — they accept whatever the model spits out, ship it, and wonder why the PR gets nitpicked to death. Cohort B treats the model like a senior pair programmer who types fast but occasionally hallucinates. They prompt for architecture sketches first, ask for edge-case tests, demand explanations for non-obvious decisions. The second group ships features in week two that used to take a month.
The difference isn't talent. It's whether they learned prompt engineering as a discipline instead of a party trick.
What changed concretely #
Boilerplate is dead. A junior who knows how to describe a REST endpoint in plain English gets a working OpenAPI spec, DTOs, validators, and a test scaffold in thirty seconds. They spend their energy on the business logic that actually matters.
Debugging became teachable. Instead of staring at a stack trace for hours, they paste the error plus context into the model, get three hypotheses ranked by likelihood, and test the top one. They still need to verify — but they're verifying, not guessing.
Code review feedback loops tightened. Seniors used to drown in nitpicks: naming, formatting, missing null checks. Now the junior runs a pre-commit hook that catches 80% of that. The review conversation starts at architecture, not style.
The new junior skill set #
- Writing prompts that encode constraints (latency budgets, dependency policies, observability requirements)
- Reading generated code critically — spotting the subtle off-by-one the model missed
- Knowing when notto use the model (hot paths, security-sensitive crypto, anything where "good enough" isn't) - Building eval harnesses so they can measure whether a prompt change actually improved output
Where it breaks #
The model doesn't know your codebase. It doesn't know the implicit invariants your team relies on. A junior who blindly applies generated migrations to production learns this lesson exactly once.
Also: the market still prices "years of experience" as a proxy for judgment. A six-month engineer with great AI habits can outproduce a three-year engineer who refuses the tools — but the resume screeners haven't caught up. That gap will close, but it hasn't yet.
The takeaway #
If you're hiring: stop filtering for "knows React internals." Filter for "can articulate a problem clearly enough that an LLM solves it correctly on the first try." That's the durable skill.
If you're a junior: your value isn't typing speed. It's the ability to direct a non-deterministic reasoning engine toward a deterministic, correct, maintainable outcome. That's a senior skill now — and you can learn it in months, not years.
Next Dutch privacy watchdog orders Twitch users to opt out of Amazon →