Google Multivac
neil.fraser.name
neil.fraser.name
His science fiction was always speculative, but in as many places as possible it was anchored to the reality he knew.
Simple amazing.
Oh, and yeah, Google is scary how big, powerful, and... omnipresent it has become.
I have to wonder - is this guy wearing headphones because:
a) Google's a hip and groovy place to work and he is allowed to listen to whatever music he wants as long as he gets his job done.
b) It's noisy in there and he needs ear defenders.
c) http://www.marshallbrain.com/manna1.htm begins at Google, and that's a wireless headset connected to a Google automated manager/instruction system. Please take one server unit from repair area D2. Thank you. Go to Server container N14. Thank you. Please identify yourself and enter. Thank you. Please locate rack 8, on your right. Thank you. Please identify the red and black power lead, and unplug it. Thank you. Please locate the network lead and unplug it. Thank you. Please slide the server out and replace it with the repaired one. Thank you. Please reconnect the network and power leads. Thank you. Please take the removed server back to repair area R2. Thank you. Please report to task room 3 for your next task. Thank you.
Edit: Nor antenna. Probably not wireless headphones.
Saying "probably ear protection" is rather missing the point of my post, and getting three upvotes for it suggests that I wasn't at all clear enough.
Point being: imagine the kerfuffle if it turned out he was being guided by an automaton task master using wireless headphones and systemic feedback from many smart sensors in the style of the coming Google power grid monitoring system - picking up a server from repair bay D2 detected, entering the server room detected, sliding a server detected and the server's details taken by RFID'd and putting a new one in, details from RFID, booted and configured and brought online automatically, old server returned and asset tracked.
Google already design their own servers and server rooms, they track power usage and memory errors and disk failures and have kernel modifications to track resource usage by program. It's not that far out, and is the sort of major thing they might do quietly which might only leak out initially by a slightly odd picture or a disgruntled insider comment.