Most developers I know treat manual coding as a muscle — skip it too long and it degrades. Fair enough. But that’s not the skill worth worrying about.
When you drive instead of riding a bike for a month, you don’t forget how to pedal. You adapt. The fear of “forgetting syntax” because you’re not writing it by hand is the same category of anxiety — and about as useful.
The skill that’s actually degrading is quieter: knowing how to think with an LLM. When to trust it. When to verify. When to throw the output away and rethink the prompt instead of patching what it gave you. When the abstraction is helping, versus hiding a design mistake you’ll pay for in six months.
That’s not a passive skill. It degrades if you don’t use it.
What I try to stay sharp on:
- Architecture. The model still needs someone to make the hard calls.
- Catching wrong-but-confident output before it lands in prod. The model is never more convincing than when it’s wrong.
- Writing prompts that constrain the problem space, not just describe it.
- Knowing when to take over the keyboard entirely — some problems are faster to just do yourself.
The real danger isn’t forgetting syntax. It’s outsourcing judgment without noticing.
And if your workplace hasn’t blessed LLMs yet — spin up something at home and train yourself there. The skill gap won’t wait for the policy.