What Debugging Taught Me About Coaching a Missed Lift

A missed lift and a failed deploy look nothing alike from the outside. One is a barbell on the floor, the other is a page at 2am. But the diagnostic process I reach for is identical, and coaching CrossFit has made me a sharper engineer because of it.

Resist the Urge to Guess

The first instinct when a service degrades is to guess: "it's probably the cache," "it's probably the network." (Let's be honest, it's always a cert though...) The same instinct shows up in coaching: "just squeeze your glutes harder." Both guesses are sometimes right but often waste the one thing you can't get back — time, and in the gym, an athlete's confidence.

The fix is the same in both worlds: observe before you intervene. Watch the lift from multiple angles the way you'd read a trace across multiple services. Where does the bar path actually break down? Is it the hip, the ankle, the setup? Where does the request actually stall? Is it the query, the connection pool, the retry logic?

Isolate the Variable

Good debugging changes one thing at a time and re-measures. Good coaching does the same. If an athlete's front squat collapses, I don't rebuild their whole technique in one rep — I isolate: tempo squats to check control, a wall drill to check the rack position, a video review to check the actual breakdown point against what they felt happened. Each is a controlled experiment with a single variable, exactly like bisecting a regression.

Root Cause, Not Symptom

A patched symptom comes back. An athlete who "muscles through" a movement fault will hit the same wall at a heavier load; a system that's restarted instead of fixed will page again next week. In both domains, the discipline is to keep asking "why" until you reach something structural — a mobility restriction, a motor pattern, a race condition, a missing index — and fix that instead of the surface complaint.

The Payoff

None of this is really about barbells or backends. It's about building a repeatable process for finding the truth under pressure, then having the patience and empathy to explain that truth clearly to the person in front of you — whether they're holding a bar or reading a stack trace.