Why is I/A shorter than a standard block?
-
junglejim4322
- Posts: 4
- Joined: Sun Jul 08, 2018 1:52 am
Why is I/A shorter than a standard block?
Perhaps my knowledge of programming is incorrect, but I have always been under the assumption that the more advanced you get, the slower progression is. So wouldn't it make since for the standard blocks to be shorter than the I/A blocks?
Re: Why is I/A shorter than a standard block?
Is O I/A really shorter? If O I/A is run twice, back to back, how does that differ from running regular O? Six weeks = six weeks, and what is the difference in starting and ending weights?
Your overall progression is how much you add over some period of time. All the templates can be the same in that respect. The length of the block doesn't really matter for that.
What makes O I/A look shorter is that is just cycles through that narrower sweet spot range.
Your overall progression is how much you add over some period of time. All the templates can be the same in that respect. The length of the block doesn't really matter for that.
What makes O I/A look shorter is that is just cycles through that narrower sweet spot range.
Re: Why is I/A shorter than a standard block?
I always think of OP I/A as ticking off sessions. I force progress or re test after I finish all 9 sessions.
OP I/A can be short if you do each session with only a day rest or can drag out if you are taking a few days between.
It’s basically just a single condensed cycle to give you the ultimate freedom in volume and rest options.
OP I/A can be short if you do each session with only a day rest or can drag out if you are taking a few days between.
It’s basically just a single condensed cycle to give you the ultimate freedom in volume and rest options.