How do I know if I'm actually improving?
Not by how it feels, which is the least reliable instrument you have. Improving shows up as work you could not have produced a month ago, judged against a standard written before you started. Everything else — hours logged, videos watched, a course bar at eighty percent — measures attendance rather than ability.
A real brief with the 5 criteria it is marked against, published before you start. Read the bands and decide honestly which one your current work lands in.
Read a marking checklistThe instrument you are using is the broken one
The reason this question is hard is not that progress is invisible. It is that the thing you are measuring it with is inside the skill you are trying to measure. Judging whether your SQL is any good requires knowing what good SQL looks like, which is most of what you are trying to learn.
That circularity has a name and a well-known paper behind it: people who perform worst at a task tend to overestimate their ability most, because the competence needed to do the thing and the competence needed to recognise it being done well are largely the same competence.1 Worth knowing that the statistical interpretation of the effect is genuinely contested — but the practical lesson survives the argument intact, and the practical lesson is that your confidence is not evidence.
The second problem is smaller and more common. Rereading material makes it feel familiar, and familiarity is nearly indistinguishable from competence from the inside.2 Most people asking this question have mistaken a feeling of fluency for a change in ability — which is also why the methods that work best tend to feel worst while you use them.3
Four checks that do not depend on how you feel
Each of these replaces a judgement about yourself with an observation about a piece of work. None of them needs a product, an account or a subscription — you can run all four on paper this afternoon.
- Could you have produced this a month ago? Keep the old version. It is the only honest before-and-after you will get.
- Does it clear a standard written before you started? A checklist you wrote afterwards will describe what you happened to do.
- Can you explain the decision, not just the result? "It works" and "it works because the join is at the order grain" are different states.
- Did it come back cold? Something you can do only while the tutorial is open is not yet something you can do.
Why a percentage is worse than nothing
Almost every learning product answers this question with a completion bar, and a completion bar answers a different question: how much of the material you have been past. It rises when you watch, when you click, and when you mark something as done, none of which are evidence about you.
There is no percentage anywhere in this product, deliberately. What it keeps instead is a list of things you have demonstrably done, each with the piece of work attached that proves it — so the answer to "am I improving" is a list that got longer, and you can open any line on it and see the work that put it there. A skill you have not touched in months quietly stops counting, because a claim about what you can do today is a claim about today.
The standard has to exist before the work does
This is the part that makes the difference, and it is the part that is easy to skip. A checklist written after you finish will quietly describe what you did. A checklist written before is the only one that can tell you something you did not already believe.
Every graded brief here publishes its rubric on the page — all four bands for every criterion, in the language they will actually be applied in. There are 4 of them for SQL alone, across 26 skills, and you can read every band without an account. The brief below takes about 90 minutes.
Sources, and what each is worth
Questions that come with this one
Is a streak a sign of progress?
It is a sign of showing up, which is necessary and is not the same thing. A long streak of passive study produces a long streak and very little else. Track what you produced, not how many days you opened something.
How often should I check?
Monthly is about right for anything with judgement in it. Weekly is too often to see movement and turns into anxiety; yearly is too late to change what you are doing about it.
What if I have nothing to compare against?
Start now — do one piece of real work today and keep it. In a month it becomes the comparison you wish you had. The cost of starting is one afternoon; the cost of not having it is another month of guessing.
Can somebody else judge this for me?
Yes, and it is usually the fastest route, as long as they tell you the standard first. Feedback against an unstated standard is an opinion; the same feedback against a published checklist is something you can argue with on specifics.
Put this into practice
Reading about how to learn is the easy half. Tell us what you are actually trying to get good at, and we will build the path — the skills in the order they depend on each other, and marked work to prove you got there.
Build my path