Welcome to Field notes
Why Field notes exists, what to expect from this section, and how the methodology behind Superfly translates into the day-to-day work of training.
This is the first entry in Field notes — the part of Superfly where the methodology gets written down in plain language, and where the small decisions inside a training plan are explained rather than left implicit.
Behind superfly
Superfly is being built by two cycling enthusiasts Vidas and Andrejus. Read further posts to check our personal stories.
Why a writing section
The product page tells you that Superfly builds training around lactate thresholds and the Norwegian model. That is true and it is useful, but it is also the what. The how and the why — why an aerobic threshold session is set at exactly the duration it is, why a recovery week is placed where it is, why we avoid the mid-zone grinding that fills most self-directed training — those things deserve more than a feature card.
These notes are where we say them.
What you will find here
- Methodology pieces explaining specific training concepts in cycling terms, with citations to the underlying research where it matters.
- Race observations from the coach who writes the templates: what worked, what did not, what would change next time.
- Application notes showing how a generic methodology translates into the specific weekly structure that the software delivers.
The goal is the same one Superfly itself has: hard days hard, easy days easy, no grinding in the middle. Including in the writing.
A note on AI
Some posts here will be drafted with the help of AI tooling, and then reviewed and edited by the author before publishing. The intent is the same as the product’s intent: AI helps with the mechanical parts; the methodology and the judgement are a person’s. If a post says “we” or “I”, that is the human speaking — not a model.
If something here is wrong, tell us. It will be fixed.
