Built for the long ride: lessons from cycling and engineering

Training for a 70.3 triathlon has taught me how critical routine is. Progress comes from consistency and not skipping steps, even on the days when it would be easier to cut corners. I have also learned that success often requires doing the things you do not particularly enjoy, whether that is a tough training session or, in engineering, mundane tasks like testing setups that demand patience.
That mindset carries over directly into my engineering work. Building reliable systems is not just about the exciting design phase. It is also about following through with all the necessary steps, like the less glamorous ones. Similar to training, the discipline to stick to the process and push through discomfort is what ultimately leads to strong, lasting results.
Holding your line
For both racing and engineering, everything starts with a plan. On the bike, I think through different scenarios in advance: What if I get a flat, or it starts to rain halfway through? That preparation helps me stay calm and react quickly when things do not go as expected. In engineering, the same mindset applies. What if there is an unexpected surge in traffic? What if the system behaves differently than expected? Considering these possibilities ahead of time, building in safeguards, and preparing playbooks means we are ready to respond effectively under pressure.
I have a simple habit I carry into security-sensitive work: trust, but verify. When I cross a one-way road, I still look both ways, because you never know when something unexpected might happen. In security work, the same principle applies. Even if a code path already has a check in place, adding another one rarely hurts. More than once, that extra verification step prevented failures when new code introduced behavior no one had anticipated. It is a small habit, but it makes the system more resilient, just like double-checks in training make me a more reliable athlete.
Preparation gets you to the start line in one piece. But once the race begins, it is the subtle adjustments that make the biggest difference.
Subtle adjustments
In triathlon, I have learned how much impact small tweaks can have. Adjusting bike position, dialing in tire pressure, or refining swim form can translate into real gains over the long haul. The same principle applies in engineering at Dropbox’s scale. Even minor improvements in how we build systems can have an outsized impact when multiplied across millions of users.
But it is not always about raw performance. Sometimes the most meaningful changes are about streamlining processes or improving clarity. Rephrasing a complicated prompt or simplifying a setup flow can dramatically increase adoption of security features, like two-factor authentication. Just like in training, it is often those thoughtful, incremental changes that make the biggest difference over time.
And while triathlon may seem like a solo sport, training reminds me that no one gets stronger entirely on their own.
Riding with others
Even though triathlon is ultimately an individual race, the training process is very much a team effort. I rely on others to review my training plans, to share what worked for them when they dealt with the same injury, or even to watch me swim and point out flaws in my form. That outside perspective makes a huge difference in how I improve.
Engineering at Dropbox works the same way. We review each other’s technical specifications, ask around when we hit a tricky bug to see if someone else has solved it before, and team up on the code when a problem needs more than one set of eyes. The willingness to share knowledge and lean on each other’s experience makes the whole team stronger, and the final outcome more reliable.
Still, even with support, endurance is as much mental as it is physical.
Staying present
On the bike, I have learned that staying focused over 90 kilometers is not about thinking of the full distance. It is about breaking it into smaller, manageable pieces. I track progress in 10 km splits and focus on hitting the next one, rather than getting overwhelmed by the whole ride. Those small goals keep me moving forward and make the long training sessions feel more achievable.
The same approach works in engineering. Especially in security, where details matter, I try to split complex work into smaller chunks. Landing smaller pull requests makes the code easier to review, reduces the chance of missing something critical, and provides that positive sense of progress. Just like in training, the discipline of breaking big challenges into smaller, focused efforts helps keep momentum strong and attention sharp.
Building endurance
Training for a 70.3 taught me that having an execution plan is essential, but so is the ability to adapt. No matter how well you prepare, unplanned injuries can appear and force you to adjust. The same is true in engineering projects. Scope changes or unexpected challenges often arise, and flexibility is just as important as planning.
I also learned the value of regular checkpoints to verify progress. In training, that meant signing up for smaller test races to gauge fitness and see what still needed work. In projects, it is about defining clear milestones or running frequent demos so the team can course-correct early and avoid surprises later.
And finally, there is the sense of satisfaction. Crossing the finish line after months of training is incredibly rewarding. It is a reminder that all the small, steady efforts added up to something big. I feel the same pride when we finally ship a long-term project at Dropbox. The journey is demanding, but the payoff makes every step worth it.
Think you have the mindset?
We built a cycling-inspired puzzle that puts your planning, problem-solving, and pacing instincts to the test. No helmet required.
Powiązane artykuły
Twój zespół, Twój wkład
Zrewolucjonizowaliśmy już przechowywanie danych w chmurze, pora na rewolucję w pracy wspieranej przez AI. Wykorzystaj swój potencjał, by wraz z Dropbox stworzyć coś wielkiego.






