How long does it take to learn to code? Count your practice hours

2 October 2026 · 7 min read

There is no honest single number, because it depends on what “learn” means to you and on how many hours of real practice you put in each week. Calendar months tell you very little; hours spent writing and running code tell you a lot. So the useful move is to count your own practice hours as you go. Within a few weeks you will have a pace, and a pace is something you can plan around.

Pick the finish line first

“Learning to code” covers goals that differ enormously in size:

Automating a task. A script that renames a folder of files or tidies a spreadsheet export. A narrow goal with a clear end.
Building one thing. A personal site, a simple game, an app for a hobby. You need enough to finish that thing, not everything.
Changing careers. Fundamentals, several finished projects and interview practice. This is the long road.

When people say it is “taking forever”, the finish line was often never chosen. Write yours down in one sentence before you count anything.

Why months are the wrong unit

Two people can both say they have been learning for six months. One does half an hour on weekends. The other does two hours every evening. They are not at the same point, and months hide that completely. Hours do not.

The kind of hour matters as well. A learning week usually contains five different activities:

Watching or reading a lesson.
Typing along with the lesson.
Building something with no instructions, where you have to decide what to write next.
Debugging: reading an error, searching for it, trying a fix.
Reading documentation to find out how something works.

Lessons feel productive because they are smooth. The skill tends to build in the rougher parts: writing code that does not work, and finding out why. A week that is mostly watching and a week that is mostly building are different weeks, even at the same total.

Counting the hours on a Mac, without a timer

A stopwatch fails for the same reason it fails at work: you forget to start it, and then the log has holes. An automatic record avoids that.

Punchcard is a Mac menu bar app that notices which app is in front during your day, by name only, and prints a receipt at the closing time you set: the top five apps with a time on each line, the rest as MISC, and a day total. You never start or stop anything, and it needs no macOS permissions to work.

For someone learning to code, the receipt lines map onto the activities above:

The code editor is writing and typing along.
The terminal is running what you wrote.
The browser is lessons, searching and documentation.

The browser line is the vague one. If you switch on “Itemize websites” in Settings, browser time in the supported browsers prints as the sites you used, each on its own line: the course site, the documentation site, the video site, the question-and-answer site where you look up errors. Punchcard keeps only the site name, never the full address, search terms or page title. Private windows are never read, and sites under a minute stay on the browser’s own line. Safari time always stays as one line; why website time tracking skips Safari explains the reason and the options.

Learning happens across weeks, so the week roll that prints on Sunday is the number to watch, and the month roll shows the trend. Tracking never expires and the CSV export works without a license. The first two printed receipts are free; printing after that is a $9 one-time license.

Reading the receipt honestly

Once you have a week or two, look for these patterns:

Editor plus terminal is your hands-on number. This is the one to grow. If it is a sliver of the total, you are studying programming more than you are programming.
The video site is bigger than the editor. You are watching more than doing. Try pausing each lesson and building the example yourself before you see the answer.
The error-lookup site is large. That is normal, and it is learning. Debugging is part of the job at every level.
Five days are empty and one is huge. A long weekend session with nothing in between means relearning on Saturday what faded since last Saturday. Shorter sessions on more days usually hold better.

The limits are worth stating plainly:

Time in front is not the same as learning. If the editor sits in front while you think, or while you look at your phone for a few minutes, that still counts as editor time.
Punchcard has no projects or tags. If you also code for work, or use the same editor for notes, the editor line holds all of it. Note the start and end of your practice blocks, then find those blocks in the CSV, which has one row per session with a start, end, app and seconds.
Anything away from the Mac is invisible: a class, a book, exercises on paper, a lesson app on a phone. Add those by hand.

How to track time while studying on a Mac covers the general version of this for any subject.

Turning hours into a forecast

The record becomes an answer to the original question when you pair it with milestones. Keep a short log in a note:

The date.
Hands-on hours that day (editor plus terminal, adjusted for anything that was not practice).
One line on what you can now do: “wrote a loop without looking it up”, “finished the to-do app with no tutorial”, “fixed a bug by reading the error”.

When you hit a milestone that matters to you, write down the running total of hands-on hours. After two or three milestones you have something no article can give you: your own rate. Say your first finished project arrived at forty hands-on hours, and your weeks average five. That is eight weeks per project of that size, for you, at your current schedule. If the next goal looks about three times as big, you can do the arithmetic yourself, and you can see what changing the weekly hours would do to the date.

This also protects you from the two common mistakes. One is quitting because progress feels slow when the record shows you have only put in a dozen hours. The other is believing you have studied for months when most of it was watching. Both are cured by the same thing: a count you did not have to remember to keep.

Questions

Should practice hours include watching tutorials? Count them, but separately. Total hours show your commitment; hands-on hours show your practice. The gap between the two is the most useful thing the record tells you.

Does Punchcard see my code or what I search for? No. It records app names, and site names if you switch itemizing on. It never records window titles, file names, keystrokes, search terms or screen contents. The record is a file on your Mac, with no account and no cloud.

Can I share my progress with a study group or mentor? Yes, as a picture or text. Each receipt exports as a 1080x1350 PNG, or you can copy it as plain text. There are no team features, so each person’s Mac keeps its own record.