How I Got There
Running a marathon is never just about race day.
The Munich Marathon 2025 was the result of a long and structured process, built over months of training, adjustments, and learning. There were no shortcuts and no single breakthrough moment — just consistency and gradual improvement.
Preparation was focused on sustainability rather than peak performance.
The priority was building endurance, learning to manage effort, and understanding how my body responds over long distances. Pace, fatigue, and recovery mattered more than chasing ambitious targets.
Training was not always linear.
Some weeks went exactly as planned, others required adaptation. Fatigue, minor issues, and schedule constraints were part of the process, not exceptions. Learning when to push and when to step back was as important as the workouts themselves.
Race day in Munich was about execution.
Staying controlled, respecting the plan, and adapting to conditions mattered more than the final time. The marathon confirmed something simple but essential: preparation shows up when it matters, even if the result is not perfect.
This experience reinforced a core principle I apply both in running and in technical projects:
progress comes from consistency, feedback, and realistic decisions, not from forcing outcomes.
The Munich Marathon was not an endpoint, but a reference point — a concrete experience to build on.
A marathon is not a single day.
It is the sum of all the ordinary days that come before it.