Building a three-month study plan

Why you need a plan

Without one, studying becomes wandering: a video about databases today, a course in another language tomorrow, an article about architecture the day after. Knowledge accumulates and none of it assembles into anything.

The plan needn't be rigid. It exists so that at any moment you know what you're doing and why.

The principle: three months to a first project

Not to a job — to a first finished thing. That's a realistic goal you can hold in your head.

Then the cycle repeats: the next three months are a second project and topping up whatever the first one exposed.

A twelve-week structure

Weeks 1–4. Language fundamentals. Variables, data types, conditions, loops, functions, lists and dictionaries, files, error handling.

Goal by month's end: write a hundred-line program without consulting a textbook every five minutes.

Practice from day one: at least two hours of your own work per hour of theory.

Weeks 5–6. Tools. Version control, the command line, debugging, virtual environments.

Goal: keep a change history, work with branches, and investigate errors yourself.

Weeks 7–8. Data. How tables work, selecting with conditions, sorting, joining. Connecting a database to your own program.

Goal: write a simple query unaided.

Weeks 9–12. Your own project. One, small, taken to a working link.

Goal: not "make it beautiful" but finish it. One scenario end to end, deployed, with a README.

Adapting it

Reorder, but don't skip. Some people prefer data before tools — fine. Dropping a block entirely is what hurts.

Trim when you're behind. Better to finish three blocks than half-finish four.

Don't stretch the fundamentals. Still on block one after two months usually means too little practice, not too little time.

When you fall behind

Falling behind is normal, not failure. Almost nobody follows a plan exactly.

The rule: don't move the goal, cut the scope. Not "I'll extend block one by another month" but "I'll take the essentials and move on". What's missing gets picked up during the project — faster, because there you'll genuinely need it.

What to add if it's going well

From around week seven or eight it's worth finding people: an open source project or a team to build with. It accelerates everything else, because feedback appears and you stop studying blind.

And a final project built with a team gets finished noticeably more often than a solo one: an agreement with people holds better than a promise to yourself.