There's more overlap between grappling and troubleshooting infrastructure than I initially expected. Both require composure, systematic thinking, and the willingness to start from first principles when you're stuck.
I started Brazilian Jiu-Jitsu a few years ago, and I've been doing IT infrastructure work for over eight years. For the longest time these were completely separate compartments of my life. Then I started noticing the same mental patterns appearing in both places.
This isn't a motivational post about "discipline carries over." It's more specific than that. There are concrete thinking patterns from BJJ that have directly changed how I approach technical debugging. Let me try to explain what I mean.
When you're in a bad position on the mat — bottom of side control, someone heavier working to take your back — the instinct is to panic and explode. The problem is that panic burns energy and usually makes your position worse. Experienced grapplers learn to breathe, assess, and move with intention even when things are uncomfortable.
A production outage triggers exactly the same instinct. Especially when it's a customer environment, or when something important is down, or when you don't immediately know what's wrong. The urge to start clicking around and trying things is strong. In my experience, that approach usually extends the outage.
The discipline of pausing to assess — what do I actually know, what do the logs say, what changed recently — is trained behaviour, not natural instinct. BJJ accelerated my ability to do that in high-pressure technical situations.
One of the first principles taught in BJJ: establish a good position before attempting a submission. Going for a choke from a bad position usually fails and leaves you more exposed.
The debugging equivalent: establish what's true before proposing solutions. I've seen engineers (and I've done this myself) jump to a fix based on a hypothesis without actually confirming the hypothesis first. You end up applying a change that doesn't address the real issue, which costs time and sometimes makes things harder to trace.
The discipline of confirming your diagnosis before acting is the same mental habit. Position first.
Drilling is important in BJJ — you build muscle memory for movements. But sparring is where you actually develop problem-solving ability, because you're dealing with a live, unpredictable partner making decisions you didn't expect.
In infrastructure, the equivalent is actually working in production or realistic lab environments — not just reading documentation. I can read every Azure networking diagram ever written. The understanding that sticks comes from deploying it, breaking it, and figuring out why. That's sparring.
BJJ has a culture of tapping out early when caught in a submission — signalling to your partner that you acknowledge you're caught, so training continues without injury. There's no shame in it. The goal is to learn, not to prove you can survive a choke.
The equivalent in engineering is asking for help earlier than pride usually allows. The engineers I respect most are the ones who say "I've been stuck on this for 20 minutes, can you look at this with me?" not the ones who silently chase problems for three hours to avoid admitting they're stuck. The goal is to solve the problem, not to demonstrate you can solve it alone.
"Both disciplines reward the person who stays calm, thinks clearly under pressure, and knows when to change approach."
I'm not claiming you need to train BJJ to be a good engineer. But if you do train BJJ, I'd bet you've noticed some of the same patterns. And if you're an engineer curious about grappling — it trains a kind of thinking that will serve you off the mat too.