⚠️ Before You Start: AI and Learning
Why using ChatGPT and Copilot while learning is a trap that harms your growth
AI during learning — like a gym trainer lifting weights for you
Imagine you want to build muscles. You go to the gym, but instead of lifting weights yourself — you ask the trainer to do it for you. Sounds absurd? That's exactly what using AI to write code while learning looks like. The result is there, but your 'muscles' stay weak.
What happens in your brain when you write code yourself
When you sit with a problem and try to solve it on your own — even if it's painful and takes an hour — important things happen in your brain:
- Neural connections form — the very act of 'getting stuck' and searching for a solution cements knowledge long-term
- Decomposition skills develop — breaking a big problem into small parts
- Working memory trains — holding several concepts in mind at once
- Intuition builds — over time you start to 'feel' where the bug is before even running the code
When you ask AI instead — none of these processes happen. You get a ready answer, but learn nothing.
A Carnegie Mellon University study (2024) showed: students who actively used AI assistants while learning programming scored worse after 3 months than those who learned without AI — even though they initially appeared to be learning faster.
Three abilities AI 'kills'
1. Critical thinking
Programming is constant questioning: 'Why isn't this working? Which approach is better? What if...?' When AI immediately gives the answer — you stop asking. Your brain gets used to receiving ready solutions and gradually loses the habit of searching on its own.
2. Creative thinking
Every programming problem has dozens of solutions. When you write code yourself — you find your own unique solution, sometimes unexpected and elegant. AI always gives the 'most typical' solution — templated, predictable. Your creativity simply isn't engaged.
3. Grit (resilience under difficulty)
The ability to 'get stuck' on a problem for an hour and not give up — one of the most important programmer skills. AI robs you of the chance to develop it. When there's no 'button' in real work — you won't know what to do.
The difference between 'cheating' and 'proper use'
AI isn't an enemy. But there's a big difference in how you use it:
| ❌ Hurts learning | ✅ Helps learning |
|---|---|
| Ask it to write code for you | Ask it to explain a concept in plain language |
| Copy solutions without understanding | Check your own solution after writing it |
| Use as a replacement for thinking | Use as a dictionary or reference |
| 'Why doesn't my code work? Fix it' | 'Explain what this error means' |
Just remember the rule: you first — then AI. Try on your own for at least 20–30 minutes. Getting stuck — great, that's learning. Only then ask for a hint (but not for ready code).
Learning is a journey, not teleportation
Imagine you're driving to a new city and want to learn the route. If you always take a taxi (AI) — you'll never remember the way. If you walk even a few times — you'll remember it forever. Same with programming: the painful path of solving something yourself stays in memory. A ready answer doesn't.
This course has an AI assistant (blue button bottom-right). Use it only to ask for EXPLANATIONS of a concept or a HINT toward the direction — but never ask it to write code for you. Your brain will thank you in a year.