One pass is a tour. Mastery takes ten.
Finish a lab once and a week later your head is blank. You do not have a memory problem. You have a repetition problem.
One pass through a lab feels like progress. Then the prompt goes blank a week later. That is not a memory problem. It is a repetition problem.
One pass shows you the shape. It does not make you fluent. The next step is to come back and do it again.
The first pass is a map
The first pass is a map. You learn where the task lives and how the grading works. Useful. Not the same as knowing the roads.
The second pass shows you what you missed. You remember the answer, not the reason. You recognize the command, not the state. That is normal. It is why you repeat.
The map is not the territory. The lab is not the job. The reps are what turn one into the other.
Completion is not skill
One completion is not mastery. It tells you that you got through the task once with the hints available. It does not tell you that you can produce the command when the system is broken, the logs are noisy, and nobody is giving you a hint. You are training for that condition, not for recognition.
Completion is a useful signal, not a verdict. The lab can tell the difference between a first pass and fluency. So can production. A green check is a receipt, not the whole skill.
Assume you will go through the important labs ten or twenty times across weeks. Not in one night. Some passes fast. Some ugly. The number is not the point. The point is that you stop treating the first completion as the finish line.
Stop collecting courses
Collecting courses feels like progress. It is not the same as practice. Another course will not fix this. Another book will not fix this. Another tab full of tutorials will not fix this. You already know more than you can execute. The missing piece is usually repetition, not information.
New courses are like new shoes. They do not do the reps for you. Pick one lab, do it until it is boring, then do it again without the hints.
The four passes
Pass one is the map. Finish with whatever help you need. Get context.
Pass two is the honest one. Close the solution. Hint only if truly stuck. Notice where you reach for help. That is your real starting point.
Pass three is recall and clarity. If you can explain the command while typing it, you know it. If not, you are still following a script.
Pass four is teaching. Explain it out loud or write it as a runbook. The gaps appear.
Space it out
Come back after three days, then seven, then longer. The forgetting is what makes the retrieval work. Daily drills keep the small commands warm. Labs cover the bigger flows. Boss fights test whether the skill survives without the training wheels.
If you only practice when you feel like it, the habit is still forming. A short schedule helps. The machine can tell the difference.
The plateau is part of the method
At some point progress stops feeling dramatic. The commands work. The labs take less time. You are not excited anymore. That is not a sign that you have peaked. It is a sign that the material is becoming normal. Normal is the goal.
It is easy to stop here because the first pass felt more exciting. The second pass is where the skill forms. What comes instead is competence, which is quieter and far more useful. Stay through the quiet part.
Work on what you avoid
Practice the weak part. The command you avoid. The flag you always look up. The error you still cannot read without guessing. Keep a short list. Start the next session there.
Boredom often means you are repeating the wrong thing. Add a constraint. Remove the hint. Do it from memory. Explain it. The comfortable commands are not the ones that get you through an outage. The ones you avoid are.
Learn the machine, not the syntax
A command is a small interface to a larger system. chmod is permissions, users, groups, and risk. systemctl is services, dependencies, logs, boot behavior. ss is the network state of a process. Repeat the command in different contexts and you start seeing the system behind it. That is when the command line becomes leverage.
Memorizing syntax is a start. Understanding the machine is the next step. The difference shows up when the command you memorized is not the command the situation needs.
How to use the labs
Do the free labs once to see the shape. Then again without the hints. Then faster. Then explain them in plain language. When you hit the paid wall, practice the free ones until the commands are boring. Then decide. The product is built for repetition, not for a single heroic weekend.
Use the daily drill to keep the small stuff warm, the boss fights to test it, and reset when you want a clean run. The tools are there. The reps are yours.
Do not wait for motivation. Motivation is for people who have not built a habit yet. The drill is small enough that discipline is enough. Three commands. One lab. Ten minutes. Then close the laptop and do it again tomorrow.
Start the second pass
The second pass is where most people quit because it feels less exciting than the first. That is exactly why it matters. Novelty is the first pass. Skill is the second and the tenth.
Open a lab you already finished. Close the solution. Run it again. Notice what you forgot. Fix that. Come back next week and do it again.
You do not have to be fluent yet. The people who look comfortable at a terminal got there through reps. The AI era is making the infrastructure layer more important, not less. The terminal is still the most honest way to reach it.
Fifteen free labs. No card. Real Ubuntu 24.04. Graded on machine state. Built for people who know the elementary commands and are ready to put in the reps. Start with one lab. Come back tomorrow. The machines will still need operators.
Run the lab again
A browser terminal with a simulated Ubuntu 24.04 environment. Repeat a lab you already finished, without the hint. Then do it again next week.
Questions people ask
How many times should I repeat a lab?
There is no magic number. If you have only done it once, you are at the start. Most people need several passes before a command feels natural. Aim for ten to twenty meaningful repetitions across different days, not ten clicks in one sitting.
Will repetition get boring?
It can, if you repeat the same easy task the same way. Change the constraint. Remove the hints. Use a different path. Explain the command out loud. Target the part that still feels slow. Boredom is often a sign that you are repeating the wrong thing.
Should I repeat the whole lab or just the commands I forget?
Both. Repeat the whole lab to keep the flow. Then isolate the commands that made you pause. A full pass builds context. A focused pass builds control.
How long does it take to become fluent?
It depends on how often you practice and how honest the practice is. A few focused sessions a week for several months will change how you work. A weekend of clicking through labs is a start, not fluency.
What if I finish all the free labs?
Do them again without hints. Then faster. Then explain them out loud. When the free labs are boring, decide whether Pro is worth it. The paid wall is not the end of the free reps.