On the road
week in week out.
Long Sunday runs, half-marathons, the occasional full distance through every German winter. Running taught me pacing. Pacing is what keeps a six-month project shippable.
I started running at a young age but only rediscovered my love for it in the last few years. It’s the one discipline outside of music and software that has taught me something genuinely useful about performance, perseverance and hard work.
My first full marathon was in 2025 and I finished it in 2:57:08, well within my (dream) target of three hours.
Pacing is the one domain where being slightly too ambitious in the first half of the race can cost you in the second half. Software timelines behave exactly the same way. The tight estimate you promise in the kickoff is the sprint you’ll be running in October.
So I pace. I keep things boring in the middle on purpose. I leave something in the tank for the last ten kilometres — the launch week, the bug bash, the handover.
The log
Back to work →
If pacing, preparation and endurance sound like useful traits in an engineer, we should talk about your project.