I started cycling this year. After the half marathon I figured I understood endurance sports, that the bike would just be running with better scenery. It isn't. Running taught me about myself. Cycling is teaching me about machines, and about what happens when you stop pretending you don't need one.
The honest sport and the leveraged one
Running is the honest sport. Everything you have is everything you are. There's nothing to tune, nothing to upgrade, no component between your effort and your result. That honesty is why I run. It's also why running has a ceiling.
A bicycle is a lever. The same legs that carry me through a half marathon at one speed carry me across three times the distance on a bike, faster, and I arrive less destroyed. Nothing about me improved on the day I first rode. The machine just took what I had and spent it better.
That sentence has been rattling around my head for months, because it's the best description I have of what I do for a living.
The engine is still you
Here's the thing people get wrong about the bike, and about every tool that amplifies you. The bike has no engine. It multiplies force; it doesn't create any. Put a stronger rider on the same frame and it goes faster. Put an untrained one on the best bike money can buy and they get dropped on the first climb by someone on a rusted commuter.
I spend my days building systems that do for organisations what the bike does for my legs. AI agents that draft and analyse and file and follow up. And the most common misunderstanding I meet is the belief that the tool is the engine. That you can buy the bike and skip the training. You can't. An agent amplifies the judgment of whoever runs it. Amplified good judgment looks like magic. Amplified absence of judgment also looks like magic, briefly, in the wrong direction.
Borrowed speed is real speed. But it's borrowed against something, and the something is still you.
Maintenance is not optional
Running shoes forgive neglect. Bikes don't. A chain you never clean gets slower every week, so gradually you don't notice, until the day you ride a friend's bike and realise how much you've been losing to your own laziness. Half a percent here, a badly indexed gear there. The bike never complains. It just quietly gives you less.
Every system I've ever shipped behaves exactly like this. Nothing fails loudly at first. It degrades politely. The search index goes a little stale, the automation misses one edge case a week, the dashboard drifts a little from the truth. The teams that thrive are not the ones with the best machines. They're the ones that clean the chain.
Drafting
One more thing the bike taught me that running never could: riding behind someone is thirty percent cheaper than riding alone. Cycling is a team sport that looks like an individual one. The group that takes turns at the front goes faster than any rider in it could go solo, forever.
I used to think asking for help diluted the work. A decade of building things has beaten that out of me, and the bike put a number on it. Take your pull at the front, then get out of the wind and let someone else work. The group arrives together, sooner. There's no prize for doing all of it alone. There never was.
I still run, for clarity. But I ride to remember that accepting leverage isn't cheating. It's engineering.