I also disagree on the relative ranking and importance of the items, but I don't feel experienced enough to really argue with them on the basis of my knowing better. Maybe in a few years.

I think a few of the points could be expanded. For example 'Robotics' gives the wrong impression and I'd say that you can get a lot of conceptual bang for your buck just from understanding the operation of basic electronics components like capacitors. It's not necessarily 'computer science' in the strict definition but being able to get an idea of how electronics and hardware items work is frankly more powerful than some of the items on this list like being able to make pretty visualizations.

Moreover, in that long list of cool languages, not a single one was a scripting language like Ruby, Perl or Python. Having one of these in your toolkit is pretty much essential and it feels like a glaring omission.

As far as the list itself, it is highly debatable. Depending on your job you won't ever need to know most of this.

Any comprehensive list of "things to know" will include things that not everyone needs to know, but it's still important to know "of" a lot of things. That way, when you encounter a new problem, you'll be reminded of something you heard about, but don't really know, and can look it up on Wikipedia.