11 Years as an Athlete Taught Me More About Software Engineering Than Any Bootcamp

I spent 11+ years in competitive fencing. Most people think sport has nothing to do with software engineering. They're thinking too small. Software engineering isn't just writing code. It's how you think, how you plan long-term, how you stay consistent when nothing is working, how you make decisions under uncertainty, and how you keep showing up day after day even when progress is invisible. That's exactly what competitive sport trains you for.

Discipline over motivation

In fencing, you train every day. Not because you feel like it, but because that's what the system demands. Some days you're exhausted, injured, or frustrated. You still show up.

Software engineering is the same. The developers who ship consistently aren't the most talented, they're the most disciplined. They write code when it's boring. They debug when it's frustrating. They ship when it's scary.

Systems beat willpower

A good coach doesn't tell you to "try harder." They build a training system: warm-up, drills, sparring, recovery. Every session has structure.

I approach development the same way. I don't rely on bursts of productivity. I have a daily system: plan, build, test, ship, review. The system does the heavy lifting, not my mood.

Pressure is a feature, not a bug

In a fencing match, you have seconds to make decisions. You learn to think clearly under pressure, to commit to a decision even when you're not 100% sure.

Shipping software has the same dynamic. You'll never have perfect information. At some point, you have to commit, deploy, and iterate based on real feedback, not hypothetical scenarios.

The transition

When I moved from athletics to engineering, I didn't start from zero. I brought a decade of discipline, pattern recognition, and the understanding that consistency compounds. The arena changed, but the principles didn't.