My personal web site's home page is 2KB. It's HTML5, no CSS, no JS. My research group site has a bit of all three plus a handful of images and comes in at 125KB. Big website I sysadmin weighs in at 1.1MB. A nice variety there. I think my personal site claims the crown as the fastest loading and quickest to render.

Perhaps across the board things aren't so good, but at the institution I graduated from (University of Bristol), most everyone from CS I've seen since I graduated 2 years ago has a decent job, or is now studying for a PhD.

Endnote would be my primary example, but I use Mendeley instead.

For some services such as wifi there are instructions for various flavours of OS - Windows, Mac, Linux, Android. We have Enterprise WPA2 and the university requires you to install their certificate, but they've done a pretty decent job of documenting it for these OSes. Unfortunately some of the software they advocate is very Microsoft or Windows centric. The Computer Science department goes quite a bit further - its lab machines run CentOS. Up until a couple of years ago there were some old Sun machines knocking about somewhere in the Engineering Faculty.

On brief reflection, I realise this is a very personal response, and doesn't really work at a level where you're working in the capacity of sysop at a medium to large company. But the question is a bit ambiguous, and this is slashdot, so pleh!

10 years is not that long, but more to the point, if I am looking for a file on media that is so old, then it must be archived not backed up. A backup is something you keep if you want to safeguard against loss of data on whatever you use as an active data store. An archive is somewhere safe you keep something when you no longer have a regular need to access it, but may still need it in the future. The methods and media for backups and archives are often the same/similar, but in the case where you have something archived, one would assume there is no "live" copy and therefore the archive should itself be backed up.

Given the rate of storage capacity expansion and my comparatively pedestrian storage requirements, my archive policy is that it stays on my computer, and simply doesn't get accessed. That way it's always backed up using my most current backup regime (rsnapshot at the moment), my "archive" isn't really an archive at all, and I don't have to worry about the media getting old, because it's guaranteed to be on my most recent media - the media I use daily.

THANK YOU!

This is so far from a secret it's not even funny. Imagine if we'd only just discovered what those two pins on the connector did?

Hell, even the breakout board the guy (who's original, non full page ad-encumbered article can be found here) bought has the bloody serial pins labelled.

It's not remotely surprising that an embedded device has a UART on it. It's even less surprising that a device designed to interface with very simple dock devices has a UART exposed via its peripheral connector.

What is surprising is that the combination of breakout board and RS232 line driver somehow managed to be bigger than the phone.