I understand that this article is probably a bit longer and more detailed than you bargained for. And if you’ve made it this far, congratulations! There’s a lot of technical mumbo-jumbo littering this piece, and knowing myself, I’ve probably got side-tracked and gone off on a tangent once or thrice. So as a reward, I want to present a case study. And using this real-world example, I want to show exactly what I did from a programming standpoint, down to the last detail, so that some method can be put to the preceding madness.
So let’s jump right into it!
The case study we’ll be analyzing is…*drum roll*…Me 🙂
Or better said, me from 2018 when I was laser-focused on bodybuilding and my programming was fine-tuned down to the last detail.
Rather than copy/pasting everything into tables and trying to organize it to not be the world’s biggest eye-sore, I’m just going to leave the link to my training log.
BRYCE’S SUPER AWESOME PERFECT TRAINING
Note that this is my commentary to myself. There are LOTS of abbreviations that might make absolutely zero sense without a legend to translate, much of the feedback I left myself is as comments on the cell (hover your cursor over the cell to view), and I don’t think it’s a reach to say that the specific implementation was suboptimal in a lot of ways. Even though I knew I was experimenting back then, I should have NEVER been programming for myself and I’m probably lucky that I didn’t come out of that with more aches/pains than I did. But on the other hand, I made more progress during this period than any other time in my life.
So feel free to look through the training log in its entirety, from the progressions to the summaries to the specific use of exercises to the changes made from meso to meso. My hope is that seeing and reading this can help tie together some of the high-level conceptual stuff that’s been put forth throughout this article. And if your brain is complete mush right now, hopefully the case study can at least spark some cool ideas next time you sit down to program!