Why Learning Notes Beat Progress Percentages

A progress bar answers “how much?” It rarely answers “what changed?” or “what should I try next?” For technical learning, the useful unit is often a small piece of evidence: the error you fixed, the behavior you observed, or the question you still cannot answer.

Percentages hide the interesting part

“JavaScript: 68%” looks precise but does not tell you whether you can explain event loops, debug a promise chain, or design a test. The number creates a feeling of movement without preserving the reasoning that produced it.

A useful note has three parts

1. Attempt: what you tried to build or understand.
2. Result: what happened, including the surprising part.
3. Question: what you want to resolve next.

Notes make review possible

A future review can connect a conclusion to the note that supports it. If the evidence is thin, the review should say so. This is more honest and more useful than silently changing a skill percentage.

The return visit starts faster

When you reopen a note, you recover the context of the last session. You do not have to reconstruct why you opened the documentation or what failed yesterday.

FAQ

Are percentages useless?

They can summarize a larger body of evidence, but they should not replace the evidence or pretend to measure mastery by themselves.

How long should a note be?

Start with three sentences. Add detail only when it helps your future self reproduce or question the result.