Pilot fish with a great memory takes us back, if not to the Stone Age, then pretty close: the time of 300-baud modems and floppy disks that were truly floppy and measured a whopping 8 inches. He’s working for a company that troubleshoots clients’ computer problems, and one mid-afternoon a customer from the other side of the state calls. Send me the data so I can investigate, fish tells them, but at 300 baud, copying it over takes most of what remains of the workday. Fish expects to be working late on this problem.
But the new office manager wants it solved same-day, and then proceeds to pretty well sabotage her own desires. First, she interrupts every couple of minutes for updates. Fish patiently explains that the only way to expose the data and find the bug is to insert “Print” statements into the code, recompile it, and then run it to see the results. The compile process takes many minutes, as does the test run. Each full test cycle takes about 15-20 minutes — pretty much an eternity in the office manager’s eyes.
To read this article in full, please click here