Skip to main content

Information Overload, Needles, and Haystacks: Part One

So this is a little more subjective than most posts I want to make here, but it still fits better than on either of my other blogs. Do I have too many blogs? That will have to do, until I get around to utilizing more proper and tag-supporting blog software. Anyway...

The internet is a amazing. The myriad of information is just fascinating, and would be overwhelming, if it were possible for any one person to truely grasp just how much data there really is out there. Not only can we not possibly grasp it, but there is no way to really utilize it. We make baby steps, every day, to obtaining more and more of that information. Or, rather, we make steps in obtaining more specialized and exact pieces over a wider selection of that information. The ammount of information we can take in has pretty much maxed, I think. All we can do now, is utilize that limit by being more intelligently selective of what is available for us to take in.

The Needle is something you want, and maybe you know it, or maybe you have no idea. The Haystack is, of course, the internet. How do you find the Needle in the Haystack, especially if you don't know you're looking for it? We need to understand what form the Needly may take, because it could be a lot of things. Is it an informational piece of text, a multimedia entertainment stream, or maybe a small tool you could utilize for your own uses? It could be any number of things, but maybe the most important part of understand what it is, is understanding that you might not know. Convergence of all the types of Needles is a necessity to finding what you want, because so often, we really don't know what it is we are looking for, even vaguely.

Next part will dive into how we bring all these different types together, and more on just how small those needles can get.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad. Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems. There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day. The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad. You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You u