Learning Programming as an Adult: A 90-Day Plan

Learning to program while holding a job does not mean studying six hours a day. It means a fixed slot, one resource, and one small project you finish. This plan runs 90 days on one hour on weekdays and three at the weekend.

Before you start: one decision, one resource

Pick one language: Python if your work is admin or data, JavaScript if you lean towards the web. The important part is not changing it for 90 days.

• One learning resource, a course or a book, finished end to end.
• One code editor and one runtime, no side experiments.
• A plain notebook for what you learned each day.

Many people we train at Q8DM start from zero while working full time. The fixed slot separated them, not talent.

Weeks 1-3: fundamentals in one language

The goal is to write a small program from scratch. Not every detail, just something that runs.

• Variables and data types: text, numbers, lists.
• Conditions and loops: if, for, while.
• Functions: take an input, return a result.
• Reading and writing files, and handling errors simply.

An hour a day covers one lesson and two exercises; the weekend is for longer ones. Do not move on until you can write a small program unaided.

Weeks 4-6: small tools that touch your own work

Pick three tasks from your working day and turn them into small scripts.

• Clean a spreadsheet and standardise date formats before the monthly report.
• Rename a batch of files or photos into one consistent pattern.
• Collect numbers from several files into a single table.
• A reminder that prints overdue tasks from a text file.

Every tool must solve a problem you actually have. A script you use weekly teaches more than ten exercises, the same approach we take at Q8DM with internal tools.

Weeks 7-9: one project, version control, other people's code

Choose a project sized for three weeks, not three months: a small web page showing your data, or a command-line tool producing a weekly report.

Learn basic Git in the same period: commit, branch, push to a repository. Your work stays safe and shareable.

Read a small open-source project for half an hour a week. It builds a sense of structure lessons cannot give you.

Weeks 10-12: deploy and collect feedback

A project nobody can reach does not count. Put it on simple hosting, or share it with a colleague who will use it.

• Write a short page explaining what it does and how to use it.
• Ask two people to try it and note the first three problems.
• Fix those problems, redeploy, record the difference.

How not to quit, and what not to do

Most people do not stop because programming is hard. They stop because it lost its slot. Fix the time first.

• Fixed slot: the same hour every day, even just half an hour.
• One resource: do not open a second course halfway through the first.
• Public log: post your progress weekly, even one line. Visible commitment pulls you back.
• The five-minute rule: on a bad day, open the editor and write five minutes only.

Do not collect courses: ten open courses equal zero progress. Do not chase every new language you hear about, or compare yourself with someone coding eight hours a day.

Do not wait for a perfect environment. Start with a simple editor and improve later. What matters is finishing one small project in 90 days and seeing it used.

Want a clear plan and a trainer to keep you on it? Visit q8dm.com to see the programming and design training programmes.