I am a junior developer and worried I am not learning
Keep using AI and change what you ask it. Move as many requests as you can from "write this" to "explain this" and "why would you do it that way?" Then do one small task a week with no assistant at all. That one task is how you find out what you have really learned.
What is going on
You ship tickets. Reviews pass. And you have a quiet suspicion that you could not have written half of it alone. That suspicion is worth listening to. Your job rewards finished work, and the AI finishes work. Nobody is measuring what you can do without it, so you have to.
There is some evidence on what makes the difference. In a trial with 52 mostly junior developers learning a new library (Shen and Tamkin, Anthropic, 2026, a preprint that is not peer reviewed), those who mostly asked the AI conceptual questions kept learning, and those who handed the task over learned less. The subgroups were very small, so read it as a direction, not a result you can rely on.
What to do this week
Ask "why" before "write"
For anything new to you: "Explain the approach and the trade-offs. No code yet." Try to write it. Ask for code only for the part you are stuck on.
One line per change you keep
For every AI change you accept, write one line on why it works, in the commit message or your notes. If you cannot, ask until you can.
One AI-free task a week
Small and real: a bug, a test, a utility function. Start to finish with the docs and no assistant. Note what was hard. That list is your study plan.
Ask a person once a week
Take one "why do we do it this way?" question to a senior colleague. They know things about your codebase that no AI does.
What not to do
- Do not quit AI to prove a point. Your team uses it, and working well with it is part of the job.
- Do not compare your speed with seniors who use AI. They are handing off things they already know how to do.
- Do not hide the worry. "I want to understand this properly" is a sentence managers like to hear.
The honest limit
This will make you slower for a while, and not every team has patience for that. If yours does not, keep the weekly AI-free task in your own time and the "why" questions at work, since those cost almost nothing. It will not make you a better engineer by a set date. It will show you where you stand.
Some coding assistants have a learning mode that leaves parts of the code for you to write. What the learning modes do now.
Questions
Will AI replace junior developers anyway?
We do not know, and nobody else does either. What you can control is being someone who understands the code they ship. That is useful in every version of the future.
What should I learn without AI first?
Whatever you will use every week: your main language, your framework's core ideas, reading a stack trace, your team's codebase. One-off scripts can stay with the AI.
How do I tell my lead I want to slow down?
Do not ask to slow down. Ask for understanding: "On this ticket I would like to write the core part myself and have AI review it." Small, specific and easy to agree to.