Guide

Teaching yourself a skill: how to track the hours you actually put in

Updated November 2026 · by Jerry Liu, Dayflow's founder

Start with a kitchen timer and a paper log: write the time you start, the time you stop, and one line on what you practiced. Add a weekly tally on a calendar. If you mostly learn on a Mac and keep forgetting to log, Dayflow (free, our product) records your screen and writes a timeline you can check. It will not see practice away from the screen.

You decided a few months ago to learn Spanish, or Python, or watercolor. Some weeks went well. You remember one long Saturday when something finally clicked. But if someone asked how many hours you have actually put in, you would be guessing, and the guess changes with your mood. On a good day it feels like a lot. On a bad day it feels like nothing at all.

Nobody keeps the record for you when you teach yourself. There is no class schedule, no teacher taking attendance, no transcript. Twenty minutes before work, a tutorial at lunch, an evening that went to installing the right software and never got to the lesson. It all blurs together.

This guide covers why self-taught hours are so hard to count, six low-tech ways to track them honestly, and where an automatic record of your screen can fit in. One disclosure up front: Dayflow, which publishes this article, makes a Mac app that does that last part. Most of what follows needs nothing more than paper and a timer.

The short version

Why do my learning hours never add up?

Memory is a poor accountant for effort. A frustrating hour feels like three. An easy, absorbing hour feels like ten minutes. When you look back over a month, you remember the dramatic sessions and forget the quiet ones, so the total you carry in your head is shaped more by feeling than by the clock.

Setup also hides inside learning time. Finding the right video, updating a tool, tidying your desk, rereading yesterday’s notes to remember where you were. These feel like part of the work while you do them, and they quietly eat sessions. Many people discover that a “two-hour session” contained much less actual practice than they thought.

Then there is the difference between taking in and doing. Watching a tutorial, reading a chapter or scrolling through examples feels productive because you are learning something in the moment. Practice, where you try and fail and try again, is slower and less pleasant, so it is easy to drift toward input without noticing.

Finally, self-teaching usually happens in scraps. A session here, a missed week there. Without a fixed slot, there is no natural point where you look back and count. If this sounds like your whole day and not only your learning, the where did my day go page covers that broader problem.

None of this means you are lazy or bad at learning. It means you have no record, and you are trying to do the record-keeping in your head.

What counts as a learning hour?

Before you track anything, decide what you are counting. This sounds fussy, but without a rule, every session gets judged differently depending on how you feel that day.

What to do: Write two or three categories on the inside cover of a notebook. A simple set is practice (doing the skill yourself), input (videos, books, courses) and setup (tools, organizing, finding materials). Decide which ones go toward your weekly total. Many people count practice and input but log setup separately so they can see it.

Illustration: Someone learning to code writes on the first page: “Practice = writing code that runs or fails. Input = reading docs, watching lessons. Setup = installing things, configuring the editor, choosing a course.” On Tuesday they spend 40 minutes fighting an install and 20 minutes on an exercise. The log says 20 practice, 40 setup, not “an hour of coding.”

After a week: You should be able to say how much of your time went to each category without guessing. If you keep hesitating over which label to use, your categories are too fine. Merge them until each session takes a second to classify.

Bookend every session with a timer and one line on paper

The most reliable tracking method is also the dullest: a start time, a stop time and one sentence, every time.

What to do: Keep a small notebook or a printed sheet right where you practice. When you sit down, write the time. Set a kitchen timer or a phone timer for whatever block you planned. When you stop, write the stop time and one line about what you actually did. If you prefer a printable layout, the daily work log template works fine for learning sessions too.

Illustration: A page might read: “7:10 to 7:45, practice. Conjugated 10 irregular verbs out loud, got stuck on two.” Then: “12:30 to 12:50, input. Grammar video on the subjunctive, half-understood.” Two lines, under a minute to write.

After a week: Count how many sessions have both a start and a stop time. If most do, the habit is holding. If you keep forgetting the stop time, write the expected stop time at the start, then just cross it out and correct it when you finish. If the notebook keeps wandering off, tape it to the place you practice.

Tally the week where you can see it

Individual sessions are noisy. One long day and one skipped day look dramatic on their own, but the weekly total tells the real story.

What to do: Pick one moment each week, such as Sunday evening, to add up the notebook. Write the total in a paper wall calendar, a sticky note on the fridge, or the margin of next week’s page. Use the same unit every time, hours and minutes, and keep the categories separate if you use them.

Illustration: A person learning guitar adds up their week: 2 hours 20 minutes practice, 50 minutes input. They write “2:20 / 0:50” in the Sunday box of the kitchen calendar. After a month the row of boxes shows a dip in week three, which lines up with a busy stretch at work.

After a week: The test is whether you did the tally at all, and whether the number surprised you. A surprise in either direction means the log is doing its job. If you want to see how learning fits around everything else in your week, the where does my week go calculator gives a rough picture in a few minutes.

Write down what you made, not only how long

Hours tell you whether you are showing up. They do not tell you whether showing up is working. Adding a small note about output keeps the log honest.

What to do: At the end of each session, add one concrete result to your line. Something you finished, something you can now do, something you got wrong and understood. Keep it specific enough that you could check it later. This is close to what people do in a work journal, and the guide to work journals has more ideas if you like the habit.

Illustration: Instead of “45 min watercolor,” the line reads “45 min watercolor. Painted the same tree three times, third one has a clean wet edge.” Two weeks later, flipping back shows exactly when wet edges stopped being a problem.

After a week: Read the output notes in a row. If they show movement, even small, your method is working. If they all say roughly the same thing, or most say “watched a video,” that is useful information. The hours may be fine while the approach needs a change, like more practice and less input.

Guess the length first, then check

Self-taught learners often plan sessions that are too ambitious for the time they have, then feel bad when they fall short. A quick guess before each session gives you a way to calibrate.

What to do: Before you start, write a short goal and how long you think it will take. When you stop, note the real time next to it. Do not try to hit the estimate. Just record both. If you want a feel for how your sense of time compares with a clock, the short time estimation test is a simple exercise, not a diagnostic. There is also a longer piece on why people underestimate how long things take.

Illustration: “Goal: finish lesson 6 exercises. Guess: 30 min.” Actual: 55 minutes, because exercise 4 needed a reread of lesson 5. Over a week, the pattern shows that anything with a new concept takes nearly twice the guess, while review sessions land close.

After a week: Look at the gap between guesses and actuals. You are not looking for perfect accuracy. You are looking for a pattern you can plan around, like “new material takes longer than I think” or “I always guess review sessions too long.” Next week, plan with that in mind.

Practice with someone else on the clock

Sometimes the problem is not counting the hours. It is getting the hours to happen. A scheduled session with another person creates a record almost by accident, because you both know when it started and ended.

What to do: Ask a friend, classmate or someone learning the same skill to meet at a set time, in person or on a video call. You do not need to work on the same thing. You each say what you plan to do, work quietly, then say what you got done. This is often called body doubling, and there is a plain guide to body doubling if the idea is new. Log the session in your notebook as usual.

Illustration: Two friends, one learning Japanese and one learning to draw, meet on a call every Tuesday and Thursday from 8:00 to 9:00 in the evening. At 8:00 they each say one goal. At 9:00 they each say what happened. Both write “8:00 to 9:00” in their logs without having to think about it.

After a week: Compare the weeks with shared sessions against weeks without. If the shared sessions are the only ones that reliably happen, that tells you what to keep. If the shared time turns into chatting, set a rule like ten minutes of talk at the end and none before.

Where seeing your actual day helps

If most of your learning happens on a Mac, the weak point of a paper log is remembering to write anything. A quick tutorial turns into ninety minutes, the timer was never set, and filling it in later from memory is exactly the guessing you were trying to get away from.

Dayflow records your screen and has AI write the day into a readable timeline, so a record exists whether or not you remembered to start anything. Full recordings and the timeline are stored on your Mac. With Local AI, a supported model runs on your Mac and screenshot analysis stays on-device. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device, and the local and cloud processing page explains the difference. You can export a date range as Markdown from Settings → Export and copy your learning blocks into your log.

Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month, and it needs macOS 14 or later. AI summaries can miss or misinterpret work, so check that a block labeled as a tutorial was really practice before you count it. Product details here come from Dayflow’s own documentation and settings for version 2.2.0, reviewed on September 6, 2026.

Dayflow publishes this article, so weigh that as you read.

Where Dayflow is the wrong pick

Be clear about the limits before you install anything.

If you would rather press start and stop on a timer yourself, look at a manual time tracker for Mac instead, or simply keep the paper log.

The bottom line

Tracking self-taught hours is mostly about replacing a feeling with a record. Decide what counts, write down start and stop times with one line about what you did, add it up once a week, and note what you produced so the hours mean something. Guessing ahead of time and practicing alongside someone else make the record easier to keep and more useful to read.

Paper and a timer handle most of this. If your learning lives on a Mac and the log keeps slipping, an automatic screen record can fill the gaps, as long as you check what it says and remember it cannot see anything that happens away from the screen.

Frequently asked questions

How do I track hours spent learning a new skill?

Write the start time when you sit down, the stop time when you get up, and one line about what you did. Keep it on paper next to where you practice. At the end of each week, add up the entries and mark the total on a calendar. The weekly total matters more than any single session, and the one-line notes tell you whether those hours were practice or setup.

Does watching tutorials count as practice hours?

It counts as learning time, but it helps to log it separately from practice. Watching someone else solve a problem feels productive, and many people find their hours look healthy while their skills stay flat. Use two labels in your log, such as input for videos and reading and practice for doing the thing yourself. If input keeps outweighing practice week after week, that is worth changing.

How many hours a week should I spend learning a skill?

There is no number that fits everyone, and any figure you see quoted depends on the skill, your goal and your schedule. A better approach is to pick an amount you can repeat every week without dreading it, log it honestly for a month, and then adjust. A steady small total you actually hit tells you more than an ambitious target you keep missing.

What is the best way to log practice time for guitar, piano or drawing on paper?

A paper notebook and a kitchen timer beat Dayflow here. Dayflow only sees what is on your Mac's screen, so an hour of scales on a real piano or sketching in a pad leaves no trace in its timeline. Keep a small log on the music stand or desk, write the start and stop times, and note one thing you worked on. It is cheap, fast and records exactly what happened.

Is it better to track time or track progress when learning a skill?

Track both, but keep each simple. Time tells you whether you are showing up. Progress tells you whether showing up is working. A good habit is a single line after each session naming something you made or can now do, like a finished exercise or a phrase you can say without notes. Hours without output can hide a stalled method, and output without hours makes plateaus hard to read.

Can a Mac app track my learning hours automatically?

Yes, if the learning happens on your screen. Dayflow records your Mac's screen and has AI write the day into a readable timeline, so you do not need to remember to start a timer. Recordings and the timeline stay on your Mac. AI summaries can miss or misinterpret work, so check the blocks before counting them, and keep a paper log for anything you practice away from the computer.

Is Dayflow free for tracking study time?

Dayflow is $0 and MIT licensed, and it runs on macOS 14 or later. There is an optional Pro plan at $20 a month, where Dayflow manages the cloud analysis. You can also use local AI on your own Mac, which keeps screenshot analysis on-device, or connect your own cloud provider, whose charges and privacy terms apply. The free app does not include paid API usage.

Does Dayflow block distracting websites while I study?

No. Dayflow does not provide website blocking. It is a record of what was on your screen, not a tool that stops you from opening anything. If distraction is your main problem, a blocker or a change of setting will do more for you. Some people use a record afterward to see what actually pulled them away, then decide what to block or move out of reach.

What should I do if I miss a week of logging my practice?

Start again with the next session and leave the missed week blank rather than filling it in from memory. A reconstructed week tends to be rounder and kinder than the real one, which makes the whole log less useful. Look at what changed that week, such as travel, a deadline or a lost notebook, and put the log somewhere harder to skip, like on top of your laptop or instrument.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required