In any case, that's funny, I bet Hofstadter based the example on this story of the Black Team.
Or is my understanding of a tape drive incorrect, and they would wind and unwind at a set rate? Because the original article said that it would often stop, rewind, move forward to retrieve data.
Also, I think the point is that it's the Black Team's job to minimize bugs shipped, and they were really impossibly good at it. It was the programmers' job to write bug-free code, and this guy was inspired by the Black Team to write perfect code. It seems like both sides were doing exactly what they were supposed to do.
There's the classic story of "Walking Drives" from esr/jargonfile:
http://dictionary.die.net/walking%20drives
Or search for "washing" here for the story about huge DEC drives being ripped apart: http://www.rinkworks.com/stupid/cs_drives.shtml
Old hardware employed a lot of force, so "bad things" (TM) really could happen.
Actually, I probably wouldn't, because if it had occurred to anyone that they ought to ensure that the bridge design had no high-Q vibrational modes, the problem would have been found and averted before the first caisson was sunk.
That's the problem with "elite" teams in organizations. You don't get the actual elite. You just get the best connected, and they think they're untouchable.