(from this discussion)
you are a more complex software project than anything from Apple, IBM, etc.
your consciousness gets to audit the software and do maintenance and add features. the heart of the software was written in childhood and you don't remember much of it. think of it like a different team of programmers wrote it, and now you're coming in later.
you don't have full access to the source code for your audit. you can see source code for little pieces here and there, run automated tests for little pieces here and there, read some incomplete docs, and do manual tests for sporadic chunks of code.
and your attitude is: to ignore large portions of the limited evidence available to you about what the code does. that is, the best evidence of what the code says available is your own behavior. but you want to ignore that in favor of believing what you think the code does. you think the conclusions of your audit, which ignores the best evidence (your behavior – actual observations of the results of running code), and doesn't even know that it's a software audit or the circumstances of the audit, should be taken as gospel.
you find it implausible there are hostile software functions that could be running without your audit noticing. your audit has read 0.001% of the source code during the last year, but you seem to think the figure is 99%.
introspection skills means getting better at auditing. this can help a ton, but there's another crucial approach: you can learn about what people in our culture are commonly like. this enables you to audit whether you're like that in particular ways, match behavior to common code, etc. b/c i know far more about cultural standard software (memes) than you, and also i know what the situation is (as just described and more) and you don't, i'm in a much better position to understand you than you are. this doesn't apply to your idiosyncrasies, i know even less than you about those, but i know that and avoid claims about the areas where i don't know. on the other hand, i can comment effectively when you write down the standard output (as judged by category and pattern, not the exact bits) of a standard software modules, at length, and i recognize it.
for more info relating to intelligence, listen to my podcast about it.