I finished my first Olympic triathlon and immediately started thinking about what was next. That's probably a character flaw. But it's also the same instinct that has me studying for my CCNA while working full time as a network analyst — there's always a next summit, always another protocol to understand, and the gap between where you are and where you want to be is just a training plan waiting to be written.
I didn't expect endurance sport to change how I approach technical study. But the crossover is almost exact. The same things that work in a training block work in a study block. The same things that derail an athlete derail a student. Same protocol, different medium.
★ THE PARALLELS ARE NOT A METAPHOR
I mean this literally. The structure of building toward an Ironman and the structure of building toward the CCNA are functionally identical once you strip out the surface details.
Structured weekly sessions
Progressive overload
Race-specific simulation
Taper before event
Recovery built in
Daily study blocks
Harder material over time
Practice exams under pressure
Light review before exam
Rest between sessions
The athlete who skips base-building and jumps straight to race pace gets injured. The student who skips foundational concepts and jumps straight to practice exams gets confused. The order matters because the adaptations stack. You can't compress real preparation into a shorter timeline without losing something.
★ CONSISTENCY BEATS INTENSITY
The biggest mistake I see in both domains is the intensity trap. The athlete who trains hard for two weeks and burns out. The student who crams for a weekend and retains nothing. Both are optimizing for the wrong metric.
In training: 45 minutes at zone 2, five days a week, beats two-hour sufferfests three times a week. The aerobic base builds on small sessions stacked over months.
In studying: 45 minutes of focused review daily beats four-hour weekend sessions. Long-term retention builds on small sessions stacked over months.
The math is the same. The timeline is the same. The discipline is the same.
My current CCNA schedule is built exactly like a training plan. I have a target date. I work backwards to figure out how much material I need to cover per week. I build in review days the same way a training plan builds in easy days. I don't skip the easy days — they're doing work even when they don't feel like it.
★ WHERE I'M AT RIGHT NOW
Routing and switching feel solid because I live them at work. Wireless is mostly practical knowledge from managing the Fortinet AP. Automation and programmability is where I need to put in the hours — that section doesn't have a work equivalent to lean on. It's pure study.
★ THE ONE MENTAL SHIFT THAT CHANGES EVERYTHING
In endurance sport, there's a concept called trusting the process. When you're three months into a training plan and you haven't done anything that feels hard yet, it's tempting to second-guess whether the easy days are doing anything. They are. The adaptation happens below the surface.
Technical study works the same way. The days when you review material you already know and nothing feels new — those days are doing work. Repetition builds recall speed. Recall speed matters in a timed exam. The easy review session at the end of a long work day is not wasted time.
The Ironman is years away. The CCNA is months away. Both will happen on the same schedule: deliberately, incrementally, and without shortcuts. One packet at a time._