§5.1 · Progress Isn't Pretty
Mastery Is Repetition with Feedback
Practice doesn’t make perfect. Perfect practice makes improvements.
That is what separates a hundred wasted hours from a hundred that actually move you forward. The reps you log have to be deliberate, they have to be honest, and they have to teach you something the next time you show up.
You can see it clearly in cybersecurity, where penetration tests are our version of reps under pressure: simulated real-world attacks run across teams, infrastructure, and products. We don’t go easy, and we don’t telegraph the punch. Sometimes we don’t even tell the blue team it’s happening, because defenders don’t get a warning in the real world, and if we want to build muscle memory we need to simulate the actual weight. That is what perfect practice really means: not pristine, flawless action, but high-quality, high-context repetition.
Malcolm Gladwell’s 10,000 Hour Rule, popularized in Outliers, offers a compelling headline: do something for 10,000 hours and you’ll become one of the best in the world at it. What often gets forgotten, and what Gladwell himself has acknowledged, is that the number only matters if those hours are deliberate, structured, and improving. It is not just any reps that get you there, it is the right reps, and that holds in lifting, in product, and in leadership.
The Lifting Lens: Periodization and Progression
Walk into any well-run gym and you’ll see programs: 5/3/1, the Texas Method, Juggernaut, Conjugate. Each one offers structure, progression, and intentional overload, and each is built on periodization, which just means you cycle through intensities, movements, and recovery phases on purpose. It isn’t sexy, but it works.
Chad Wesley Smith, founder of Juggernaut Training Systems, built JTS by emphasizing smart lifting over heavy lifting. As he puts it:
“Motivation gets you started. Discipline keeps you going. Feedback tells you where to go next.” — Chad Wesley Smith, founder of Juggernaut Training Systems
I use the JuggernautAI app myself. It takes in feedback on how I move, how I recover, and how I progress, then adjusts the plan accordingly, so every session has a purpose. It is a coach in your pocket, and a reminder that great outcomes come from smart, consistent reps.
Lifters learn something else the hard way: showing up and doing something beats waiting for the perfect plan. A light session with focused movement and intention will beat a skipped workout every time, and small improvements made consistently compound into real strength.
The Product Mirror: Disciplined Iteration at Elastic
When Elastic Security shipped its initial security analytics and SIEM product in 2019, it wasn’t a complete answer to the market. It was a start, informed by users, opinionated in structure, and designed to evolve. What made it successful wasn’t just the launch, it was the loop: weekly user feedback, signal from real-world deployments, and disciplined iteration sprints that followed a clear roadmap.
Each product cycle was a planned lift, part of a broader program of growth, not a shot in the dark. Features like detection rules, case management, and timeline didn’t just “appear.” They were reps, refined under load. We looked at how users engaged, what didn’t click, and what needed retraining, and we built telemetry into the stack, not to track vanity, but to see where improvement was possible.
The discipline scales beyond security. Watch how Anthropic has rolled out Claude from 2023 through 2026: a deliberate cadence of model versions, capability updates documented in public changelogs, and a clear deprecation path that respects the developers building on the platform. Claude 3 to 3.5 to 4 to 4.5 to Opus 4.6 was not a series of sudden leaps. It was a planned program of reps, in public, refined under load. The market saw the releases, and the team felt the loop.
Reps With a Purpose
Whether you’re logging lifts or logging bugs, the idea is the same: feedback closes the loop. Reps without it just reinforce habits, good or bad. Reps with it are where you find progress.
Athletes track tempo, range, and fatigue. Product teams track usage, drop-off, and latency. Neither discipline rewards brute force for long, but both reward the people who show up, take notes, and come back better.
In the gym, a lifter might swap from high-bar squats to pause squats to work through a sticking point. In product, a team might start dogfooding an unfinished feature to catch friction early. In both cases the rep is the mechanism, and the lesson comes from how you interpret it.