What to do in your first 90 days of learning to code

This is the plan I give mentees who tell me they want to learn to code and don't know where to start. It assumes no experience, no money, and about an hour a day. Ninety days is enough to get genuinely useful — not job-ready, but past the point where you'd quit.

Weeks 1–2: One language, no shopping around

Pick Python. Not because it's best, but because it's forgiving, it's readable, and the answer to any question you have is already on the internet. Deciding between languages is procrastination wearing a helpful face.

Work through variables, conditionals, loops, functions, and lists. Type every example rather than copying it. When something doesn't work, read the error message all the way to the end before doing anything else — this one habit is worth more than the next three weeks combined.

Weeks 3–4: Build something small and stupid

A dice roller. A tip calculator. A script that renames every file in a folder. The project doesn't need to be impressive; it needs to be yours and it needs to run. Tutorials give you the illusion of understanding, and the only way to find out what you actually know is to build something nobody wrote instructions for.

Weeks 5–6: Learn Git before you need it

Learn four commands: git init, git add, git commit, git push. Put your dice roller on GitHub. It will feel pointless with one file. It is not pointless — you are starting the public record that eventually replaces having a CV with nothing on it.

Weeks 7–9: Something with data

Find a CSV of something you care about — match results, transit times, game statistics — and write a script that answers a question about it. Read the file, process it, print the answer. This is the shape of an enormous amount of real programming work, and it's the point where most people start finding it fun instead of dutiful.

Weeks 10–12: Put it in front of a person

Wrap one of your scripts in something someone else can use. A command-line tool with proper arguments, or a tiny web page with Flask. Then hand it to a friend without instructions and watch where they get confused. Everything that confuses them is a lesson you can't get any other way.

Rules that make the ninety days work

• Same time every day. Thirty consistent minutes beats a five-hour Sunday. Momentum is the whole game.
• Struggle for twenty minutes, then ask. Less than that and you learn nothing. More than that and you're just eroding your own morale.
• Keep a log. One line a day about what you did and what broke. On the days it feels like nothing is happening, the log is the evidence that it is.
• Don't compare your week 3 to someone's year 3. Everyone posting confidently online was once staring at an indentation error for an hour.

Ninety days doesn't make you a developer. It makes you someone who has proved to themselves that they can learn this, which is the harder part.

If you'd like someone to check in with you through those ninety days, that's precisely what our mentors are for.