Why More Practice Can Make You Worse, and Why Commutes Might Secretly Improve Your Thinking

Hatched by Dhruv

May 05, 2026

10 min read

4 views

62%

The uncomfortable truth about improvement

What if the fastest way to get better is not to do more, but to notice more? That question sounds almost offensive in a culture that worships volume. More tests, more hours, more hustle, more repetition. Yet some of the most meaningful gains come from the opposite move: stepping back, observing patterns, and extracting signal from experience.

That is where two seemingly ordinary ideas become surprisingly powerful together. One is the link between commuting, productivity, and innovation, the other is the claim that quality of analysis matters more than the number of tests taken. On the surface, one is about time spent in transit, the other about test preparation. But underneath both is the same deeper tension: does progress come from accumulating experiences, or from transforming them into insight?

The answer is not just philosophical. It changes how you study, how you work, and even how you think about wasted time.

The myth of linear effort

Most people imagine improvement as a straight line. If one mock test helps, ten should help more. If one hour of thinking is good, three hours should be better. If a commute feels like lost time, then eliminating it should automatically improve productivity. This logic is tidy, intuitive, and often wrong.

Why? Because not all effort has the same function. Some effort creates raw material. Other effort turns raw material into usable intelligence. A person can take twenty tests and learn very little if each test is treated like a score report rather than a diagnostic instrument. Likewise, a person can spend an hour in transit and gain nothing if the commute is filled with reactive scrolling, fragmented attention, and low-grade mental noise.

The real difference is not whether time is spent, but how the mind is allowed to work inside that time. This is why some commutes become surprisingly generative. They create a bounded interval, separated from the demands of immediate execution, where the brain can wander, connect, and recombine. In the same way, a well-analyzed mock test creates a bounded interval after performance, where the brain can convert mistakes into pattern recognition.

Experience without reflection is just consumption. Reflection without experience is just speculation. Progress lives in the loop between them.

That loop is where productivity becomes innovation and practice becomes expertise.

Why transit can sharpen thought

It is tempting to think of commuting as dead time because it is not directly convertible into output. But that is a narrow definition of value. Some forms of thinking require a softer, less aggressive mental environment. A commute can provide exactly that, especially when it creates enough distance from immediate tasks to let the mind organize itself.

Consider the difference between trying to solve a problem at a desk versus during a walk or train ride. At the desk, the mind often becomes tactical. It asks, What is the next step? During transit, the mind can become structural. It asks, What is the pattern here? What am I actually doing wrong? What would make this easier next time? That shift matters because innovation rarely emerges from brute force alone. It often appears when the brain is not clenching.

This is why many people do their best thinking in the shower, while driving, or on public transport. The body is occupied, but the executive mind is slightly released. That release gives subtle associations room to surface. It is not magic. It is cognitive spacing. The commuter is not just moving through geography. They are moving through mental frames.

A useful way to think about this is to distinguish between execution mode and integration mode:

Execution mode: focused, task-specific, linear, useful for doing.
Integration mode: diffuse, connective, reflective, useful for understanding.

A life with no integration mode becomes mechanically efficient and intellectually stale. A life with too much integration mode becomes dreamy and unproductive. Commuting can be valuable because it often forces a transition between the two.

The point is not that commuting is inherently good. The point is that it can become a container for synthesis, which is something many modern schedules lack.

Why mock tests are not really about tests

The same logic applies to learning. Many people mistake test-taking for progress because tests are measurable. You can count them, rank them, and compare them. But measurable is not the same as meaningful.

A mock test is not primarily a test of memory. It is a test of diagnosis under pressure. The score matters, but the score is only the surface. The deeper value lies in what the score reveals: where assumptions break, where attention drifts, where time management collapses, where confidence is misplaced, where concepts are weak, and where patterns repeat.

This is why quality of analysis matters more than number of tests taken. Without analysis, a mock test becomes a ritual of performance. With analysis, it becomes a map. The student who takes five tests and reviews them deeply may improve faster than the student who takes fifty tests and only glances at the answers.

Here is the core misunderstanding: most people think the test is the training. In reality, the test is the mirror. The training begins when you look long enough to see what the mirror is actually showing you.

A strong analysis process usually asks questions like these:

What was the real cause of the error? Not just the wrong option, but the faulty reasoning.
Was this a knowledge gap or a judgment gap? Many mistakes are not about not knowing, but about choosing badly under uncertainty.
Did time pressure change my behavior? Some errors only appear under stress.
Was this a one-off miss or a repeating pattern? One mistake is data. Three similar mistakes are a system problem.
What rule or cue would prevent this next time? Analysis should end in a usable correction.

This is the difference between collecting experiences and converting them into competence.

The hidden common structure: bounded time that changes behavior

The deeper connection between commuting and mock test analysis is not obvious at first, but it is elegant. Both are bounded experiences that, when used well, change how the mind organizes itself.

A commute is a bounded stretch of time where direct action is limited, which creates room for reflection. A mock test is a bounded stretch of time where performance is compressed, which creates pressure that reveals weaknesses. One opens the mind, the other exposes it. One is a space of wandering, the other a space of stress. Yet both are productive only when followed by interpretation.

This gives us a powerful framework: productive time is not defined by intensity alone, but by whether it produces usable insight.

Think of it like photography. You can take hundreds of photos, but if you never inspect lighting, focus, composition, and subject placement, you are just generating files. Analysis is the darkroom. It is where raw exposure becomes an image. Commutes can function like the pause between shots, a chance to notice what the frame needs. Tests function like overexposed moments that reveal where the picture falls apart under pressure.

When people complain that they have no time, the issue is often not time scarcity. It is insight scarcity. They are moving through events without capturing what those events mean.

The real productivity bottleneck is often not effort. It is interpretation.

That is why a long commute can become useful and a long study session can remain wasteful. Time itself is neutral. The critical variable is whether the mind is converting experience into a better model of reality.

A better model: treat every experience as a diagnostic

If commuting and mock tests share a hidden structure, the practical lesson is broader than either one. We should stop dividing life into productive and unproductive chunks based only on visible output. Instead, we should ask a more intelligent question: What kind of thinking does this time enable?

This leads to a useful mental model:

1. Capture

First, gather the experience. This might be a mock test, a commute, a meeting, or a conversation. At this stage, the goal is not to optimize. The goal is to observe what happened.

2. Decode

Next, identify patterns. Where did attention drift? Where did stress distort judgment? Where did a neutral stretch of time produce a useful idea? Decode means moving from event to explanation.

3. Distill

Then convert the observation into a rule, cue, or habit. For example: "When I miss the first two questions in a section, I rush the next five." Or: "My best ideas come after ten minutes of uninterrupted transit, not while multitasking."

4. Deploy

Finally, use the insight in the next cycle. Insight that never changes behavior is just interesting noise.

This framework turns both commuting and testing into part of a larger learning system. The commute becomes a place for integration. The test becomes a place for diagnosis. Together, they form a rhythm of pressure, reflection, correction.

That rhythm is how growth actually happens.

What this changes in daily life

Once you see this structure, several common assumptions start to look outdated.

First, a commute is not automatically wasted time. It is wasted only if it remains unstructured and unexamined. A person who uses that time to think through a difficult decision, mentally review mistakes, or let a problem settle may gain more than someone who gains twenty extra minutes at a desk but never steps out of reactive mode.

Second, taking more tests is not inherently better. More tests can even harden bad habits if they are used as entertainment, reassurance, or ego management. The right question is not, How many did I take? The better question is, What did I learn that changed my next attempt?

Third, innovation is often misdescribed as a sudden spark when it is really the product of a well-managed cycle. Exposure, pause, analysis, recombination. The spark often appears at the end of that sequence, not at the beginning.

A practical example makes this concrete. Suppose two students prepare for the same exam:

Student A takes fifteen mocks and checks the score.
Student B takes six mocks, but after each one writes down recurring mistakes, classifies them, and creates a correction list.

At the end, Student B may outperform Student A not because of more effort, but because of more informative effort. Student B transformed each test into a feedback engine.

Now imagine two professionals with identical schedules. One uses commuting time for fragmented scrolling, then sits down and starts work from a mental fog. The other uses commuting time to rehearse a difficult conversation, sketch priorities, or think through a design problem. They arrive with different mental states, and over time, different careers.

Small choices about how to use in-between time can compound into large differences in judgment.

Key Takeaways

Do not confuse activity with progress. More tests, more hours, and more motion only help if they produce clear insight.
Use bounded time for bounded thinking. Commutes can support reflection and synthesis; mock tests can reveal weaknesses under pressure.
Analyze patterns, not just outcomes. A wrong answer or a bad section score is valuable only when you identify the underlying cause.
Build a feedback loop. Capture, decode, distill, and deploy what you learn from every meaningful experience.
Protect integration time. Not all productive thinking looks like focused work. Some of it looks like quiet transit, walking, or simply letting the mind connect dots.

Conclusion: the real skill is not doing more, but seeing better

We often praise people for their discipline, but the deeper trait behind real improvement is epistemic humility: the willingness to admit that experience alone does not teach enough. Experience must be interpreted. A commute that feels empty may be full of thought. A mock test that feels disappointing may be full of data. The difference is whether you are willing to mine it.

This is the reframe worth keeping: productivity is not just the ability to produce output. It is the ability to turn time into understanding.

Once you see that, the question changes. You stop asking, How much time did I save? and start asking, What did this time teach me? You stop asking, How many tests did I take? and start asking, How much did each test improve my model of myself? That is a much harder standard, but it is also the one that leads to genuine progress.

In the end, the best learners and the best thinkers are not the ones who do the most. They are the ones who convert the ordinary spaces of life, a train ride, a failed attempt, a mistake on paper, into sharper judgment. That is where productivity becomes innovation. That is where practice becomes wisdom.