Why I built Rocky
I'm Oscar. I've always trained a lot. Marathons first, then mountain marathons, and for the last few years swimrun. I love swimrun because the training is so varied, and a race is really a string of small races, one for every swim and every run.
I also have a family, kids and a full-time job. So my training plan broke all the time. A sick child, a late day at work or a short night, and the rest of the week no longer made sense.
My watch collected a lot of data: sleep, HRV, heart rate, every session. I never had the time to turn it into anything useful. What I needed was something that could read the whole picture: what I had planned, what I actually did, how it went and how I recovered.
Then I decided to go for the Swimrun World Championship. With the hours I had, the only way to pull it off was to train efficiently, so I built something for myself. The first version was a small script that read my training data and let me talk it through with an AI. It helped enough that I kept building, and it became Rocky.
How it helped
Rocky helped me in two ways. The first was re-planning around life, so a missed session or a bad night changed the next few days instead of wrecking the week.
The second was about me. At 45 I was still training like I was 25. I didn't recover enough between the hard sessions, and the results stopped coming. Rocky saw it in my data and kept pushing me to train easier.
Just getting started
Rocky is new and we keep adding features and improvements, many of them asked for by the people training with it.
If something feels wrong or is missing, tell Rocky in the chat. It reaches us. You can also write to hello@rocky.training.
Oscar Holmberg