Quote from jack hershey:
The reigning and non hunching will happen as we move up the line. Shade your new prints as you do the Spyder answer sheet compare. Mark the ends of the shade and just score diagonally in between on some part of the width. This focuses on success, an important drill. You do not have many problem areas BUT they are there; they, mostly are self-policing once you see them and the time of day in which they occur (the more severe hunching periods, so far).
Most emanate from poor data clusters where you do not dig to assemble clouded areas data. you are tending to go back to the screen repeatedly (the source of hunching) while you ARE IN ANOTHER THOUGHT PROCESS MODE THAT DOES NOT DEAL WITH SENSORY INPUT FROM THE SCREEN. YOU MIX SENSORY SCREEN INPUT WITH m OF mada CLUSTER SUBSET INPUT. Composing M clusters is VERY DIFFERENT from surfacing the A pair from your mind WHILE NOT LOOKING AT THE SCREEN but JUST LOOKING AT THE LEFT PORTION OF THE LOG to write in the A and D parts of the LOG.
I am not yelling with caps it is just easier than the ET annotation requirements for doing emphasis type things.