The system I use for tracking my workouts is similar to the one I use for
tracking my diet. Both of them use Emacs and an org-mode file for storing
data, but my workout tracking is simpler as I'm not making entries during the
day.
A typical workout entry looks like this:
* CAL-OUT Exercise for <2020-10-26 Mon> :PROPERTIES: :beeminder: bodyweight-workouts :beeminder-skip-deadlines: true :END: ** Warm up - [X] 10 x Shoulder Band - [X] 20 x Wrist rotations - [X] 20 x Side leg raises - [X] 20 x Glute bridges - [X] 20 x Donkey kicks - [X] 90s x Dead Bugs - [X] 90s x Hollow Hold ** Strength Aim for 5-8 of each one, 3 sets total (4 optional). Rest 90 seconds between pairs. |------------------------+-------+-------+-------+-------| | Exercise | Set 1 | Set 2 | Set 3 | Set 4 | |------------------------+-------+-------+-------+-------| | Bodyweight Squat | 5 | 5 | 5 | 5 | | Pull Up | 8 | 8 | 8 | 8 | |------------------------+-------+-------+-------+-------| | Ring Hold (seconds) | 20 | 20 | 25 | | | Romanian Deadlift | 8 | 8 | 8 | | |------------------------+-------+-------+-------+-------| | Incline Row | 8 | 8 | 8 | | | Pushup | 8 | 8 | 8 | | |------------------------+-------+-------+-------+-------| | Lying leg raise | 6 | 6 | 8 | | |------------------------+-------+-------+-------+-------| ** Notes - Some soreness in the left elbow
It's a really simple mix of an org-mode checklist and a table for individual
exercises. I like how flexible tables are in org-mode, and entering
data is quick and simple.
The PROPERTIES: block is entirely optional. It uses beeminder.el to submit a
data point whenever I close the org-mode headline.
Like my diet file, adding new entries is handled by org-capture. I don't
currently extract statistics from my workout file, but it's on my TODO
list. Even without any stats it's extremely useful to look back and see where
I've improved, and the notes section reminds me of what worked and what didn't.
The routine itself is based on the /r/bodyweightfitness recommended routine.