As a programmer, I will charitably note that it’s not uncommon for a more serious bug to mask other more subtle ones; fixing the big one is still good, even if the program may look just as badly broken afterwards.
And one of the unfortunate things about the human architecture is that the more global a belief/process is, the more invisible it is… which is rather the opposite of what happens in normal computer programming. That makes high-level errors much harder to spot than low-level ones.
First year or so, I spent way too much time dealing with “hangups making this chore hard to do”, and not realizing that the more important hangups are about why you think you need to do them in the first place. So it has been taking a while to climb the abstraction tree.
For another thing, certain processes are difficult to spot because they’re cyclical over a longer time period. I recently realized that I was addicted to getting insight into problems, when it wasn’t really necessary to understand them in order to fix them, even at the relatively shallow level of understanding I usually worked with. In effect, insight was just a way of convincing myself to “lower the anti-persuasion shields”.
The really crazy/annoying thing is I keep finding evidence that other people have figured ALL of this stuff out before, but either couldn’t explain it or convince anybody else to take it seriously. (That doesn’t make me question the validity of what I’ve found, but it does make me question whether I’ll be able to explain/convince any more successfully than the rest did.)
That said, there is a lack of solid evidence, and the grandiosity of the claims suggests brilliant insight or crackpottery in some mixture
Heh, you think mine are grandiose, you should hear the claims that other people make for what are basically the same techniques! I’m actually quite modest. ;-)
And one of the unfortunate things about the human architecture is that the more global a belief/process is, the more invisible it is… which is rather the opposite of what happens in normal computer programming. That makes high-level errors much harder to spot than low-level ones.
First year or so, I spent way too much time dealing with “hangups making this chore hard to do”, and not realizing that the more important hangups are about why you think you need to do them in the first place. So it has been taking a while to climb the abstraction tree.
For another thing, certain processes are difficult to spot because they’re cyclical over a longer time period. I recently realized that I was addicted to getting insight into problems, when it wasn’t really necessary to understand them in order to fix them, even at the relatively shallow level of understanding I usually worked with. In effect, insight was just a way of convincing myself to “lower the anti-persuasion shields”.
The really crazy/annoying thing is I keep finding evidence that other people have figured ALL of this stuff out before, but either couldn’t explain it or convince anybody else to take it seriously. (That doesn’t make me question the validity of what I’ve found, but it does make me question whether I’ll be able to explain/convince any more successfully than the rest did.)
Heh, you think mine are grandiose, you should hear the claims that other people make for what are basically the same techniques! I’m actually quite modest. ;-)