I’ve been trying to sew together my ideas (I should probably say beliefs as I did not exactly invent any if this stuff) considering lifting for the past couple of days - this time in a larger scale with a couple of new things such as gasp volume work
So I’ve been thinking - hard variations, rest pause, overload work, high frequency, cycling exercises but keeping it rather simple, supports, all that good stuff into one program. It’s a hell of an project to put it together (in my heart I can see the program perfectly but I find them hard to shape, for me it’s art. The program must be beautiful even on the paper)
Then after I’ve done the version 1.0 I’ve got to test it myself and see what works and what doesn’t, what I’ve got to change and so on. That’ll take some time. I’d say that in 10 weeks the program is on stage 1.1. Which is the “obvious mistakes have been removed” - stage. At that point I should put 1-2 other people on it as well and observe them. It’ll show how different people do on the program and that’ll help me remove the flaws that do not bother me but may bother them. That’ll take like another 10 weeks or so
Then it’s stage 1.2. - the real test stage. This is where the program would be ran for a couple of months (or cycles if it is a cyclic program) to see if it is actually effective with building muscle and strength, that’ll take yet another 10-12 weeks. (If I can’t see visible change in one’s appearance in 12 weeks and they haven’t put on considerable amount of weight on their lifts I’d say that the program needs readjustment - this excludes the really advanced guys of course)
As you see, putting together a program in a way that allows you to proudly present it to other people may easily take over half a year!
So it’s not all that easy. Of course anyone can come up with a “10 exercises for this and that bodypart in these days for 3 sets of 10-15” in 20 minutes but real programming takes time. You should note that this is just when we are talking about completely new things (in this case, some new things and more old things than ever before, so it’s really a big project)
I’ve written a couple of programs before and usually I’ve had someone else (a trainee) do the test drive for me - the results have been good practically every time. But those programs were done in a much smaller scale, they focused on less things and were rather simple in nature (not that I would start writing astronomically complex programs now, that’s just stupid) but as this is a project that’s supposed to unite all of my thoughts for once, I want to test drive this myself first before I let anyone else touch it. It may be that the program ends up being too rough to do during the army, which will mean that it’ll wait until I’m out, or it may be that the program flops big time (it would surprise me, but with this many moving parts it’s a completely possible option) and I’ll just scrap it.
We’ll see, we’ll see. You can expect me to write some observations down here as well, but don’t expect me to lay out the program anytime soon.
Now I’m off to bed, I’ve got a lot to do tomorrow and my phone is dying.