I feel like SQL is a bit of a categorically different thing to the others on this list. It's best to have python (or another language) and SQL, if you're going to be in a 'coder' role.
If you're in an analyst type role, with SQL as your primary language, then SQL and Py/R is also a good thing.
The practice of offering zero-hours contracts for university lecturing has been very controversial in the UK[1] and other parts of Europe. I think they short-change the students and the lecturers, and represent a long-term risk to the institutions who use them.
Arguably the problem that is implicitly solved is 'how do we reach and target college students and graduates from the high-value Ivy League demographic?'
You're right. For me, it does point to the fact that most predictions are wrong at some point, right at some point, and irrelevant before and after. The things that was a laptop then (5kg beasts like this http://en.m.wikipedia.org/wiki/Sharp_PC-5000) were nothing like today's machines. The T1100 seems to have been the first close thing.
It's impressive to think that it took 20 years from that article for notebooks to outsell pc. http://www.theguardian.com/technology/2009/oct/28/laptops-sa... also fun to see how net books are a focus of attention for that article.
I wonder what level of accordance will be needed for a wearable to seriously compete with the current mode of computing.
How do they compare to Vibrams? I tried to get a pair of KSO or Bikila last time I was in the USA, but all the shops have stopped stocking them since the company settled a lawsuit.
If you're in an analyst type role, with SQL as your primary language, then SQL and Py/R is also a good thing.