Thinking about thinking

Most of what I do is find bugs in computer programs, but every once in a while, I sit and think about what might be wrong with my own thought process. The conclusions are usually laughable, but not funny

Example 1 (High latency):

Problem: I consider myself a slow thinker. At least, that's my excuse for being quiet person -- almost never dominating a conversation. By the time I think of something to say, others are already on a different topic

1. When I get a haircut, I usually ask to have the hair on the back/bottom of my head cut higher. Raise that line. It usually never happens.
2. One day, I share my haircut experiences with my brother, and he says the same thing happens to him. However, the barber once explained to him that his neck is real long and if there's no hair covering it, people will notice!
3. Maybe I'm like my brother, and I have a long neck?
4. Brain signals from body parts further from the head take longer to arrive at the brain (shoulder tap vs foot tap experiment)
5. Longer neck == slower thinker?
6. Haha right. I'd like to think my brain does the thinking, so a longer neck means nothing
   

Example 2 (Paging in):

Problem: It's very common for people to forget what they learn. Lagrange multipliers? Hell if I remember. I'd only remember where to look for a reference. Now, what I'm worried about is whether or not my daily routine accelerates this.

1. At "work" (i.e., school), I often need to look through GIGABYTES of boring text. Logs for debugging my own code, other people's code to see if the possible bugs my analysis program discovers are false positives (btw, if you know an efficient way to do that, let me know), etc. Sure this exercises the brain, but it teaches very little.
2. In undergrad CS classes, a common exercise is: look at what happens to caches with an LRU replacement policy when the working set is bigger than the cache. You get thrashing!
   
3. The amount of crap that streams through my brain probably exceeds whatever cache-like mechanism is in my head, hence the constant need to look things up again.
4. Thrashing in cache is probably not so bad because you still have other levels in the memory hierarchy that are relatively fast. Once you hit the disk though, you may as well forget about your computations ever finishing.
5. Is every useful thing I know on "disk" now?

Oh sorry, now that you've read this crap, you'll need to page things in as well =)