First million

Some experts hit their “first million” repetitions before most of us finish school—keystrokes, notes, lines of code, quiet drills no one sees. On the surface, nothing looks special. Here’s the twist: those invisible reps are rewiring their brains while everyone else is just “practicing.”

A weird pattern shows up when you study top performers in tech and beyond: their early practice looks boringly similar. Not glamorous “build the next unicorn” work—more like running the same function a hundred ways, fixing the same bug in ten different projects, or typing out patterns until their fingers move before their thoughts catch up. The difference isn’t that they love repetition; it’s what they *do* with it. Those who accelerate fastest quietly turn routine tasks into tiny experiments: “What if I name this differently?” “Can I do this with one less step?” “Can I predict the next error before it happens?” Over thousands of cycles, that curiosity turns ordinary work into a laboratory. The result is a strange kind of compound interest: the same number of hours, but far more learning packed into each one.

In tech, those early cycles usually aren’t heroic side‑projects; they’re the “small stuff” everyone else treats as throwaway: refactoring a boring utility, reviewing another pull request, writing yet another test. Research on skill acquisition shows these repetitions only become transformative when your brain starts tracking patterns: “I’ve seen this bug shape before,” “This API design always causes friction,” “This naming style keeps confusing reviewers.” That pattern library is what separates the engineer who just “has experience” from the one who quietly becomes the person others ask before touching critical code.