One thing I do is take notes on most things I read. Just a couple sentences. This helps in several ways:
1) If you're not willing to take notes on something, it's not worth reading. So you read less.
2) It limits your rate of consumption, because writing takes time. So you read slower.
3) Having it written down and organized reduces the burden on your brain. It's like the GTD system. You want to relieve your brain of holding information. Your brain will know it is one click away if you have organized your notes properly.
4) When writing notes, you are relating it to things you already know. It forces recall. This prevents your brain from being just a jumble of useless disconnected facts.
Notes rock. I agree with 1, 2, 3, and 4.
I like tasks and reminders in any of a variety of systems. I send myself a lot of emails to process later.
I took one of those self tests and it came back ITSJ
Please note that this is not about MB, it's about getting hints about who you are and how you use the information you seek.
I was not aware of MB until a friend IRL told me that I might be a certain type. I took the test, and from there my world seemed to open as I at least had a way to learn more about myself.
I read the term "information diet," and I think that is what it comes down to. I've had to do this time to time. Having a motivating side project to help you pick between what is and is not relevant to you at a particular time is a good idea.
Anyway, good luck.
And to put it succinctly, minimize your information firehoses and reject the notion that you need to keep abreast of everything even if it is not relevant to you.
Purge all of your reading lists and resist building them. If you keep any lists or bookmarks, require that they be things you HAVE read and want to keep as reference for later. I do have a "toread" bookmark folder, but I almost never go back to read things there.
Visit only one or two tech sites a day. For example, I come to HN to the exclusion of almost anything else because it does a good job of showing only relevant things. But I limit this to 3-5 times a week and only when I'm bored. It's a good filter.
Lastly, get a personal project that serves as a good source of challenges. Use it to help decide if you should read about a particular technical topic. You'll find that this serves as a good filter, but at the same time you'll magically seem to read about things relevant to your technical challenges in a surprisingly timely manner.
HTH,