Basically, we spend too much time trying to be smart.
What we need to do, then, is: stop reading, and start doing.
Your mind is saying, "I'm full! You can stop eating now!" It's scratching at the door to get out.
So, stop. Ask yourself, "Knowing what I now know, what do I want to do?"
Once you've picked something to do, you will doubtlessly need some information to do it. But that's okay. Because this is an active search, rather than just passively being swamped by information. It's a different type of thing entirely. So go get the information that you need, and start working on whatever it is you're working on.
You'll probably feel immense relief.
Now, after a period, your mind will not be full any more. You'll need another filling of passive information. You need "SituationAwareness?," I think they call it in the military. So you go out and look again.
Fill up. Get to the "InformationOverload" stage. Top off. Get active. Work. Yay! But now you're running low. Fill up.
After a while of going through this cycle, you start to gain some awareness of it, I think, and it becomes less disruptive. You can respond a little quicker to the InformationOverload signals.
I think that part of why PairProgramming works so well, is similar to the reason why mountain climbers teather themselves to each other. It's just a good idea. We can stay focused, and watch out for each other. It's also a reason why I think that the HiveMind could work, and that we will see a massive boost in FreeSoftware development, as we figure these things out.
AttackTheDocumentMode: I'd like to split "PersonalInformationOverload?" off from this page, to talk about the personal experience of InformationOverload, and possible solutions. This page has too much in it, right now, to be reworked.