Why the dip comes in month two
The first month runs on enthusiasm: everything is new, progress is visible daily, and "variable" and "loop" are discoveries.
In month two the easy part ends. Topics get harder, progress becomes invisible, and the result is still far off. The question "will this even work" arrives, and there's nothing to answer it with.
That isn't weak character. It's how any long learning works: musicians and athletes hit the same thing.
What helps
Count what you built, not what you studied. "Learned about functions" is vague. "Wrote a program that renames files" is concrete. Keep a list of what you've built; it will rescue you on days when you feel stuck.
Shrink the step. Planned an hour and haven't sat down for three days? Plan twenty minutes. Twenty minutes five days running beats zero.
Work on your own thing, not only exercises. A project you personally need pulls you forward when assignments have gone stale.
Leave something unfinished. Stop on an obvious small task so tomorrow has a handhold.
Change the activity. Tired of new material? Read someone's code, revisit an old program of yours, fix something. That's studying too.
What helps most
People. It's the one technique that works more reliably than all the others combined.
Alone, quitting costs nothing: nobody notices. With someone you're building a shared project with, or simply checking in with weekly, disappearing becomes awkward.
It needn't be a mentor. A peer is enough: another beginner you swap weekly progress with.
What not to do
- Don't start a new course. The temptation is strong: novelty gives a lift. But two weeks later you're in the same place, a month behind.
- Don't switch languages. Boredom in month two isn't a sign of a wrong choice. It will arrive with any of them.
- Don't stop completely. "A couple of weeks off to rest" becomes six months. Lower the pace, but not to zero.
If you did quit
Don't treat it as failure. Work out what happened: too fast a pace, dull material, no visible result, nobody to talk to.
Coming back is easier than it looks. A week is usually enough to recover the essentials — you continue rather than restart.
And when you return, change the main thing: find someone to go on with. A second solo attempt usually ends like the first.
Хватит читать — пора делать
На CohortX можно найти команду под пет-проект и получить тот самый опыт, о котором спрашивают на собеседовании.
Похожие статьи
- Python from scratch: what to learn and in what orderThe order of topics from variables to a first service, what can wait, and where people usually get stuck.
- Python с нуля: что учить и в каком порядкеПорядок тем от переменных до первого сервиса, что можно пропустить на старте и на чём обычно застревают.
- How to ask questions that get answeredThe shape of a good question, how long to struggle alone, and why asking well is valued as a skill in itself.