01 Sep 2010 15:44
More and more, everyone is learning that "diets" don't work. Sure, people drop weight on diets but they fail to make a lasting change. I don't need to go into this, you know all about yo-yo dieting. Despite this there are still plenty of judgmental folks (who probably wouldn't know a problem if it bit them in the tuchus) who will say stuff like, "jeez, what ever happened to old fashioned self-control?"
18 Aug 2010 22:52
Never assume that your authority figure is smarter than you. I constantly see trainees accepting everything a certain person says because they simply feel that they are not smart enough to apply any thought to it so they must simply absorb it as gospel.
I was looking around for Mel Siff items on the internet and came across Tony Gentilcore’s “Resource Page”. After the entry on Mel Siff’s book “Facts and Fallacies of Fitness” Gentilcore wrote:
13 Aug 2010 00:02
You may have heard trainers and coaches talk about movement amplitude. I often talk about amplitude as being one of those performance characteristics that determine the outcome of a training regimen and one of the factors indicating reductions or improvement in performance.
Amplitude is also part of the "law of repetitive motion" equation developed by Dr. Michael P. Leahy, who is the founder of Active Release Techniques (ART). This "law" is an equation describing the interaction between various parameters of human motion: I=NF/AR where:
09 Aug 2010 02:28
I'm going to give you three vegetables. You pick the best one.
- Green (Bell) Peppers
08 Aug 2010 20:46
When is a program a program and when is it programming methodology? Easy. A program is a program when you are doing it exactly as it has been written or planned. And it is "programming methodology" when somebody spins it into one. Always realize that the underlying principles that drive a "program" are more important than the program itself.
The question to ask about principles versus programs is which came first. We can use our experience with training to make many observations. While making those observations we may be using programs, or routines. We can then take these observations and derive philosophies and principles. If the observations are sound and the conclusions we make from them are sound they will apply regardless of the programming methodology. In other words they will have a good chance of being generally true rather than true only if we use a particular way of programming.