How to actually learn to code when you have a full-time job

Most people who fail at this do not fail because they lack ability or time. They fail because they used a plan designed for full-time students.

If you work, the constraint is not hours in the week. It is that your best mental energy is already spoken for. Any plan that ignores that will collapse in about three weeks.

The maths that people get wrong

Ninety focused minutes a day, five days a week, is about 32 hours a month. Across six months that is close to 200 hours — enough to become genuinely competent at one thing.

An eight-hour Saturday feels more serious and is worth less. You spend the first hour remembering where you were, you are tired by hour four, and you retain very little because retention comes from repeated exposure over time rather than duration in one sitting. It is also the first thing to be cancelled when a wedding or a deadline appears.

Consistency beats intensity here, and not by a small margin.

Pick your ninety minutes deliberately

Not "whenever I get time" — that is how it becomes never. An actual slot, the same one every day, chosen around your real energy:

Early morning is the most reliable for most people, because nothing else has started yet. It costs you sleep, so go to bed earlier; studying while exhausted mostly produces the feeling of studying.

Immediately after work, before going home — in a café, or at your desk. Works well because you have not yet dropped into evening mode. Fails if your commute is long.

After the family sleeps works for a lot of people with children and is the hardest to sustain, because your best focus is gone. Use this slot for practice and repetition rather than new concepts.

Whichever you pick, protect it the way you would protect a meeting with your boss.

What to cut

You cannot add ninety minutes without removing something. Be honest about what:

• Scrolling. Almost everyone has ninety minutes here and does not believe it until they check their screen time.
• One TV series.
• Some socialising, temporarily. Six months is not forever, and people who care about you will understand a specific plan with an end date.

What not to cut: sleep below seven hours, and exercise. Both look like free time and both make the other ninety minutes worse.

The rule that matters most: build, do not watch

The single biggest waste of limited hours is video tutorials.

Watching someone else solve a problem produces the feeling of learning without the substance. It is comfortable — that is the trap. You finish a ten-hour course, feel knowledgeable, and then cannot start a blank file.

A better ratio is roughly 20% input, 80% doing. Watch or read enough to understand a concept, then close it and build something small and slightly wrong. Get stuck. Look up the specific thing you are stuck on. Fix it. That loop is what actually installs a skill, and it is slower and less pleasant than watching.

Type the code out rather than copying it. It feels pedantic and it is the difference between recognition and recall.

The month where nothing sticks

Somewhere around week five to eight, most people hit a stretch where progress stops. You understood it last week; today you cannot write it. You start wondering whether you are one of those people who cannot do this.

Everyone hits this. It is not a signal about your ability — it is the point where easy surface knowledge runs out and real understanding has not consolidated yet.

Two things get you through. First, keep going at reduced ambition: do thirty minutes on days you cannot face ninety, because the streak matters more than the volume. Second, go back and rebuild something you made in week two. You will find it easy now, and that is objective evidence you have improved even though it does not feel like it.

Why a course helps, and what it cannot do

The honest case for structured learning when you are busy is not that the information is unavailable free — it is all free. It is three things:

A sequence, so you are not spending your limited hours deciding what to learn next. A deadline, which is the only thing that reliably beats "I'll do it tomorrow." And someone reading your work and telling you specifically what is wrong with it, which you cannot do for yourself.

Every track we run is online with recorded sessions for exactly this reason — missing one because of work should be an inconvenience, not the end of the attempt. The shorter tracks are two to three months, which is a realistic commitment for someone employed, and going deeper afterwards is a normal path rather than an admission that you started wrong.

What no course can do is the ninety minutes. That part is yours.