This is an active solicitation for suggestions on how to train it differently.
Apparently, this morning I put on my underwear wrong.
Upon noticing that they were on incorrectly, I took them off by turning them inside out on the Z axis (top of head to bottom of feet), and then rotating them 180degreees along the Y axis (belly button to back, travelling through the spine).
I noted the degrees of off-ness on the two axes, intending to remember them for the next time this happens. Yes, this happens often enough that I'll probably use the information again. Sometimes, even clothing is hard.
...
It was only then that I realized that the easier way to understand what happened would be to say that they were 180degrees off on the X axis (L shoulder to R shoulder, by travelling across the back).
------------------------------------------
Ultimately, how this seems to play out is that I get ahead of myself in some rather strange ways. I tend to think of things in motion before I fully understand them in their static forms. In the example above, it would have meant that I was trying to store larger chunks of more complex data, when a simpler notation would have done just as well. I also find that it can distract me from recognizing the context around whatever I'm observing.
I'm only just beginning to be able to identify when that's happening.
Obviously, I want to address this. I just don't know how to go about figuring out what needs to be done. From how to gather more information, to what to do with it.
Ideas?
I'm not sure this is bad. In my research (and in everyday life), often the best solution is to try to do something, anything, just perturb the system in some way to see what happens, because I find you often need a vector to start optimizing and correcting. Often I find what a desirable outcome is by taking the action of putting things in motion or thinking of them in motion.