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 operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world. Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove: All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through. Where did they all go? My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access.   I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I cou...