I didn't roam the ground floor of the computer industry, but it was only a few flights up. At college in the early 1970s, I manipulated code — not merely running programs but writing them. The field was "data processing" then, and I hammered on a keypunch machine, gashing small rectangular holes into cards. I fed these into a hopper on an IBM 360/22, a computer only a bit smaller than a Volkswagen Bug. If you happened to drop your precisely ordered batch of cards on the stroll to the CPU … well, a human was the untidiest loop in the sequence.
The class was interesting, occasionally absorbing, but not inspiring — for me, on a par with solving crosswords. Nevertheless, I did well enough to be offered a student job in the data processing department. I was already working part-time on campus, for an outfit called the line crew — "lines" being water and sewer pipe. We started as ditch-diggers, but soon learned how to lay various kinds of pipe; to install fittings, valves and control boxes, and to troubleshoot and repair system breaks. Unlike other student workers, we were dispatched in the middle of the night to tackle emergency water and sewer challenges. The job was satisfying.
The assistant director of data processing knew I worked in dirt, and when he offered me a position — on the cutting edge of the future, as he saw it — I was aware he felt like a benefactor, and rightly so.
"No, thank you, sir" I nonetheless replied, "I'd rather stay on the line crew." It was a simple statement of personal preference, but he clearly felt snubbed. He'd presented an opportunity, and I'd spurned it. Indeed, my principal work life has been blue-collar ever since, including miles of pipe and a host of muddy and/or icy trenches.
In the 40-plus years since then, most water and sewer line technology of that era has remained apropos; in computing, the tools of the 1970s vanished decades ago and are largely forgotten. Ask a smartphone user on the street: "What's a keypunch machine?" Google it.
The engineering of water distribution and wastewater collection remains static. A pipe is a pipe, and so similar in form and function to a blood vessel or a colon that pipes will probably not be much further refined. In evolutionary terms, they're like tortoises or coelacanths.
Computers are like bacteria or viruses — evolving so quickly that comparison even to brains seems inadequate. Are they mutating into their own "species?" We are the agents of that evolution, and one thing I learned back in 1972 still pertains: GIGO, garbage-in, garbage-out. Humans remain in ultimate (though not always in proximate) control of the machines. We continue to write the programs, at least for now.
Individuals often feel dragooned by computers, boxed in by a drop-down box. Despite the undisputed benefits of the digital milieu, some (many?) of us may nod and chuckle at a quip by the late Ogden Nash: "Progress might have been all right once, but it has gone on too long." Any backlash, however, is muted.