IT pilot fish is asked to take over a small project that hasn't made any progress in two years in the hands of a guy who just can't seem to find time for it -- and he doesn't have time to turn over his work to fish, either.
IT consultant pilot fish is at a client site where the business has just finished a move -- with the usual slightly chaotic aftermath -- when another building tenant stops in to announce he's getting the client's old digs.
It's a few decades back, and this technical rep pilot fish is awakened by his beeper to learn that a customer -- a college campus -- is completely without phones or data communications, and no one is sure why.
This pilot fish has spent much of his career as an executive at growing IT companies, so he seems like the perfect guy to help out an iconic IT vendor that's struggling to figure out Web 2.0 -- or maybe not.
It's the mid-1990s, and this pilot fish is a sysadmin at a local college with a dedicated phone line that's just used for testing modems. And that setup works fine -- at least until fish goes on vacation.
Second-level IT support tech needs to get a failed video card replaced, so he does the logical thing: He asks the IT service desk to open a problem ticket and call the vendor. What could be wrong with that plan?
Flashback to the late 1970s, when this military agency uses highly classified mainframes that boot from decks of punch cards. But what happens to the punch-card guy when the vendor shifts to magnetic tape?