What you can realistically manage
Someone in full-time work finds seven to fifteen hours a week. Planning twenty-five is a reliable way to collapse within a month and conclude you're incapable.
An honest seven hours a week for a year achieves more than a heroic twenty for six weeks followed by burnout.
Why weekends are a poor foundation
"Rest on weekdays, study six hours at the weekend" sounds sensible and works badly:
- A week loses more than one session gains. Every time you start by rebuilding context.
- Weekends get cancelled. Visitors, errands, exhaustion — and a month disappears.
- Six hours straight is inefficient. After the third hour retention drops sharply.
The reverse works: a little, but often.
Routines that work
Morning before work. An hour before anything else, while nobody is pulling at you. The most reliable option of all: mornings rarely get cancelled, whereas evenings may find you empty.
An hour after work, but not immediately. Give yourself a break first. Sitting down straight from a working day, wrung out, doesn't work.
Lunch. Half an hour on one small topic or problem.
Micro-sessions. Twenty minutes before bed reading someone's code or documentation. Not much, but it keeps you connected to the material.
Ideally: five short weekday sessions plus one longer weekend session for project work that needs immersion.
Keeping context
Leave something started. When you stop, don't polish to perfection — stop on an obvious small task. Tomorrow you won't face a blank page.
Keep a short log. Three lines: what I did, what didn't work, what's next. Five minutes that saves twenty getting back in.
Keep the environment ready. If starting takes ten minutes every time, you'll put it off.
What you'll have to cut
Honestly, something will go. Usually television, social media and some socialising. But not sleep and not all human contact at once — that way you'll last two months.
Studying alongside work is a year-long marathon. Plan a routine you can sustain for a year, not a sprint that finishes you in a month.
About family
Agree it in advance: how much time, which hours, until when. Silently disappearing every evening breeds resentment that later costs more than the hours saved.
What speeds things up when time is short
Building something with other people. It looks like it costs time and actually saves it: you don't grind alone for a week on something they'd explain in ten minutes.
And an agreement with people holds a schedule better than a promise to yourself — especially when, after a working day, you'd rather postpone everything.
Хватит читать — пора делать
На 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.