Ch2 02: The Action Track: Practice to Produce#

A man named Tomás sat down to learn Python. He’d done everything right by the book so far: one skill selected, Practical Threshold defined (“build a script that automatically renames and organizes my photo files by date”), environment prepared (laptop, code editor installed, tutorial bookmarked), schedule committed (weekday evenings, 7:00-8:30 PM).

On night one, he opened the tutorial and followed along for ninety minutes. He learned about variables, data types, and print statements. He felt productive. Night two, more tutorial. Functions and loops. Night three, more tutorial. File handling and libraries.

By night five, Tomás had watched or read about twelve hours of Python content. He could explain what a function was. He could describe the difference between a list and a dictionary. But he hadn’t written a single line of code that wasn’t copied from a tutorial. He hadn’t tried to build anything. He hadn’t failed at anything.

On night six, he tried to start his photo-organizing script from scratch. He stared at a blank screen for twenty minutes. He couldn’t remember the syntax for opening a file. He couldn’t figure out how to read a date from a filename. He went back to the tutorial.

Night seven, he didn’t practice at all. “I need to review more first,” he told himself.

Tomás didn’t have a knowledge problem. He had a practice problem. He’d spent twelve hours on the Cognition Track and zero hours on the Action Track. He knew things. He couldn’t do things. And in skill acquisition, the gap between knowing and doing is where most people get stuck.

This chapter is about the doing.

The Output Principle#

Here is the single most important rule for the practice phase of any skill:

In the first 20 hours, produce more than you consume.

Spend more time doing the skill than studying the skill. More time playing notes than watching lessons. More time writing code than reading about code. More time cooking meals than watching cooking shows. More time speaking the language than memorizing vocabulary lists.

The ratio doesn’t need to be extreme. Aim for roughly 70% practice, 30% study. But the direction matters: output leads, input follows.

Why? Because in early skill acquisition, the bottleneck isn’t understanding — it’s execution. You can understand how a chord transition works and still fumble it with your fingers. You can understand the grammar of a sentence and still freeze when you try to say it aloud. The gap between comprehension and performance is closed by repetition, not by more comprehension.

This is uncomfortable. Producing when you’re a beginner means producing badly. Your first sketch will look wrong. Your first conversation in Spanish will be full of errors. Your first attempt at a recipe will taste mediocre. That’s not failure. That’s the process.

The discomfort has a name in psychology: the competence gap — the distance between what you know you should be able to do and what you can actually do. Everyone experiences it. Experts experienced it too, when they were beginners. The only way through it is volume. Not better input. More output.

Quantity Before Quality#

There’s a well-known anecdote from a ceramics class. The instructor divided students into two groups. Group A would be graded on quality — they needed to produce one perfect pot. Group B would be graded on quantity — they needed to produce as many pots as possible, regardless of quality.

At the end of the semester, the best pots came from Group B.

Not because they were more talented. Because they practiced more. Each pot taught them something — about clay thickness, about firing temperature, about glaze application. The students who aimed for one perfect pot spent their time theorizing, planning, and hesitating. The students who aimed for volume spent their time doing, failing, adjusting, and doing again.

This is the Quantity Principle, and it applies to every skill in the early phase.

Don’t try to play the song perfectly. Play it all the way through, mistakes and all. Don’t try to write the perfect paragraph. Write ten paragraphs and see which ones work. Don’t try to cook the perfect omelet. Cook seven omelets this week and notice how each one gets a little better.

In the first 20 hours, your job isn’t to be good. Your job is to be prolific. Quality emerges from quantity. Not the other way around.

This doesn’t mean being careless. It means being willing to complete the whole process — start to finish — even when the result is rough. A finished, imperfect attempt teaches you ten times more than a half-finished, careful attempt.

The Speed-First Principle#

Related to quantity is speed. In early practice, move through the entire process quickly before you try to optimize any single part.

If you’re learning to cook a dish, cook the whole dish — prep, cook, plate — even if each step is clumsy. Don’t spend thirty minutes perfecting your knife cuts on the first try. Get through the whole recipe. See the finished result. Then go back and improve specific steps on the next attempt.

If you’re learning a song on guitar, play the whole song — all the chords, all the transitions, start to finish — even if you have to slow down or pause. Don’t spend an hour perfecting the first four bars. Get through the entire piece. Feel the shape of it. Then go back and work on the hard parts.

This is the Speed-First Principle: run the complete loop before you optimize the components.

The reason is cognitive. When you practice one component in isolation, you lose context. You don’t know how that component fits into the whole. You might spend thirty minutes perfecting something that turns out to be a minor part of the overall skill. But when you run the complete loop first, you get a map. You see which parts are hard and which are easy. You discover where the real bottlenecks are. Then you can invest your limited practice time where it matters most.

Speed-first doesn’t mean rushing. It means completing the full cycle, even imperfectly, before drilling down into details.

Time Block Commitment#

Here’s where intention meets structure.

“I’ll practice when I have time” is the most common commitment people make. It’s also the most commonly broken. Not because people are dishonest — because “when I have time” is a category that, for most adults, contains nothing. There’s always something else to do. Laundry, email, errands, rest. If practice has to compete with everything else for unscheduled time, it will lose.

The fix is time block commitment: pre-scheduling specific practice slots and treating them as non-negotiable.

The mechanics:

Duration: 60-90 minutes per session is the sweet spot for most skills. Shorter than 60 minutes and you spend too much of your time warming up and settling in. Longer than 90 minutes and fatigue sets in — especially for beginners, whose concentration capacity for a new skill is limited.

Frequency: Daily is ideal. Every-other-day is workable. Less than three times a week and you lose too much between sessions — the skill fades, and each session starts with re-learning instead of building.

Consistency: Same time each day, if possible. The habit loop — cue, routine, reward — works best when the cue is reliable. If you practice at 7 PM every evening, your brain starts preparing for practice mode around 6:45. If you practice at random times, your brain never gets that cue.

Protection: The time block goes in your calendar. You tell the people in your life about it. You don’t schedule over it. If something comes up, you reschedule the practice block — you don’t delete it.

Real numbers make this tangible. If you practice 60 minutes a day, five days a week, you’ll hit 20 hours in four weeks. One month from zero to your Practical Threshold. If you practice 90 minutes a day, five days a week, you’ll hit 20 hours in less than three weeks.

These are not large commitments. They’re smaller than most people think. But they require structure, not just desire.

The Fast Feedback Loop#

Practice without feedback is just repetition. And repetition without correction doesn’t build skill — it builds habits, including bad ones.

The feedback loop is the mechanism that turns raw practice into actual improvement:

Do → See the result → Compare to target → Adjust → Do again

The shorter this loop, the faster you improve. Every minute between “doing” and “seeing the result” is a minute where you can’t adjust. And adjustment is where learning actually happens.

Here’s how to shorten the feedback loop for different types of skills:

Physical skills (guitar, cooking, sports): The feedback is often immediate — you hear the wrong note, you taste the dish, you see the ball miss. The key is to pay attention to the feedback instead of powering through. After each attempt, pause for two seconds. Ask: “What happened? What should I change?” Then try again.

Creative skills (writing, drawing, design): The feedback requires comparison. Keep a reference — a photo you’re trying to draw, a piece of writing you admire, a design that represents your target level. After each practice piece, set it next to the reference. Don’t judge yourself. Just notice the differences. Those differences are your next practice targets.

Knowledge-applied skills (coding, language, analysis): The feedback comes from testing. Write code, run it, see if it works. Speak a sentence, see if you’re understood. Build a spreadsheet formula, check if the output is correct. The test is the feedback. If you’re not testing frequently, you’re not getting feedback.

The golden rule of feedback: if you practiced for an hour and can’t point to one specific thing you improved, your feedback loop is too slow.

A useful structure: set micro-goals within each practice session. Not “practice guitar for an hour” but “practice the G-to-C transition until I can do it without looking, then practice the strumming pattern for ‘Knockin’ on Heaven’s Door’ at half speed.” Each micro-goal has a built-in test — either you can do the transition without looking or you can’t. That test gives you feedback. That feedback drives the next adjustment.

The 20-Hour Timer#

Now let’s make the commitment tangible.

The 20-Hour Timer is exactly what it sounds like: a cumulative tracker that counts your total practice hours. Not study hours. Not “thinking about the skill” hours. Actual, hands-on practice hours.

You can use anything to track this: a simple tally on paper, a note on your phone, a stopwatch app, a spreadsheet. The tool doesn’t matter. What matters is that you track honestly and consistently.

Why track? Three reasons.

First, tracking creates accountability. When you can see that you’ve invested 8 hours, you’re less likely to quit. The investment becomes visible. Behavioral economists call this sunk-cost awareness — and in this case, it works in your favor. You’ve put in 8 hours. The finish line is 12 hours away. Quitting now means losing those 8 hours. Continuing means reaching the goal.

Second, tracking provides perspective. At hour 6, you might feel like you’re not making progress. But when you look back at hour 1 — at what you could do then versus what you can do now — the progress becomes obvious. Without tracking, you lose this perspective. With tracking, you can always compare “now” to “then.”

Third, tracking creates a finish line. The 20-hour commitment isn’t open-ended. It’s finite. You’re not signing up for “learning guitar forever.” You’re signing up for 20 hours. After 20 hours, you assess. Did you reach your Practical Threshold? If yes, you’re done — or you choose to continue because you want to, not because you have to. If not, you adjust your target or invest another focused block.

Feedback Checkpoints: Every 5 Hours#

Within the 20-hour container, set four checkpoints — one every 5 hours.

Hour 5: Orientation Check#

You’ve been practicing for roughly a week (at 60-90 minutes per day). Ask yourself:

Can I identify the 2-3 sub-skills that are hardest for me?
Am I spending most of my time on core sub-skills (not peripheral ones)?
Is my practice environment working, or do I need to adjust something?

This checkpoint is about direction. Making sure you’re practicing the right things, not just practicing.

Hour 10: Progress Check#

Halfway. This is the most dangerous point — far enough to feel tired of being a beginner, not far enough to feel competent. Ask yourself:

Can I do things now that I couldn’t do at hour 1?
If I recorded myself at hour 1 and now, would I see a difference?
Am I still aiming at my Practical Threshold, or have I unconsciously raised the bar?

That last question is critical. Many people, once they start improving, shift their target upward. “I thought I just wanted to play three songs, but now I want to play ten.” That’s fine as a future goal — but right now, it moves the finish line and makes the commitment feel open-ended again. Keep your original target. Reach it first. Then expand.

Hour 15: Threshold Preview#

Three-quarters done. You should be able to attempt your Practical Threshold test — the testable target you defined earlier. You might not pass it cleanly. That’s fine. The point is to try.

Attempt the test. Note what works and what doesn’t. Use the remaining 5 hours to focus specifically on the gaps the test revealed.

Hour 20: Threshold Test#

Do the test for real. Can you perform the skill at the level you defined?

Three signals tell you that you’ve crossed the Practical Threshold:

Execution without constant reference. You can do the core parts of the skill without looking things up every thirty seconds. You might still check occasionally, but you’re not dependent on instructions.
Usable output. You can produce something functional — a meal people enjoy, a song people recognize, a script that runs, a conversation that flows. Not perfect. Functional.
Shifted feeling. The emotional experience has changed from endurance to engagement. Practice no longer feels like something you’re forcing yourself through. It feels like something you’re choosing. This shift is subtle but unmistakable.

If all three signals are present, congratulations. You’ve crossed the threshold.

If you’re close but not quite there, you have a choice: invest another 5-10 focused hours, or accept that your threshold definition might have been slightly ambitious and adjust it.

What Tomás Should Have Done#

Back to Tomás and his Python project.

Here’s the Action Track version of his first week:

Night 1 (90 min): Spend 20 minutes on a tutorial covering the absolute basics — variables, print statements, how to run a script. Then spend 70 minutes writing tiny scripts. A script that prints his name. A script that calculates how old he is in days. A script that asks for input and responds. Small, complete, working programs. Each one taking 5-15 minutes. Each one producing a result he can see.

Night 2 (90 min): Spend 15 minutes learning about file operations from a tutorial. Then spend 75 minutes writing scripts that interact with files — create a file, write text to it, read text from it, list files in a folder. Each script is ugly. Each script works. Each script teaches him something the tutorial didn’t cover — like what happens when the file doesn’t exist, or when the path is wrong.

Night 3 (90 min): Start building his actual project — the photo organizer. Not the whole thing. Just the first piece: a script that reads the filenames in a folder and prints them. Then a script that extracts the date from a filename. Then a script that creates folders named by date. Each piece is small. Each piece is testable. Each piece gives feedback.

By night three, Tomás has written maybe fifteen small scripts. Most are messy. Several had errors he had to debug. But he’s built things. He’s seen results. He knows what it feels like to write code that runs. He’s on the Action Track.

The difference between “learning about Python” and “learning Python” is the difference between reading a map and walking the road.

The Practice Mindset#

I want to close with a shift in perspective that makes all of this easier.

Most people think of practice as the price they pay for skill. The work. The grind. The thing you endure to get the reward. And in the early hours, it can feel that way.

But somewhere between hour 5 and hour 15 — the timing varies, but it happens for almost everyone — something changes. You stop dreading the session and start looking forward to it. You stop counting the minutes and start losing track of them. The endurance transforms into something closer to play.

This is the third signal of the Practical Threshold: the shift from endurance to enjoyment. It doesn’t happen because you’ve gotten good. It happens because you’ve gotten just good enough to experience the skill from the inside — to feel the rhythm of the song, to taste the seasoning you chose, to see the code run and do what you told it to.

You don’t need to wait for this shift. You don’t need to force it. You just need to keep showing up, keep producing, and keep shortening the feedback loop. The shift takes care of itself.

Don’t wait until you feel ready to start practicing. Starting to practice is how you become ready.

Set your timer. Open your notebook. Pick up the instrument. Turn on the stove. Write the first line of code.

The next twenty hours are already shorter than you think. And the only one who can start the clock is you.