"You mean you don't stage the software?" I asked him. "You don't test it?" "Why should we? Everything we do is live all the time, always new, minute … - Ellen Ullman

IV. Real techies don’t worry about forced eugenics. I learned this from a real techie in the cafeteria of a software company. The project team is having lunch and discussing how long it would take to wipe out a disease inherited recessively on the X chromosome. First come calculations of inheritance probabilities. Given a population of a given size, one of the engineers arrives at a wipe-out date. Immediately another suggests that the date could be moved forward by various manipulations of the inheritance patterns. For example, he says, there could be an education campaign. The six team members then fall over one another with further suggestions. They start with rewards to discourage carriers from breeding. Immediately they move to fines for those who reproduce the disease. Then they go for what they call “more effective” measures: Jail for breeding. Induced abortion. Forced sterilization. Now they’re hot. The calculations are flying. Years and years fall from the final doom-date of the disease. Finally, they get to the ultimate solution. “It’s straightforward,” someone says. “Just kill every carrier.” Everyone responds to this last suggestion with great enthusiasm. One generation and — bang — the disease is gone. Quietly, I say, “You know, that’s what the Nazis did.” They all look at me in disgust. It’s the look boys give a girl who has interrupted a burping contest. One says, “This is something my wife would say.” When he says “wife,” there is no love, warmth, or goodness in it. In this engineer’s mouth, “wife” means wet diapers and dirty dishes. It means someone angry with you for losing track of time and missing dinner. Someone sentimental. In his mind (for the moment), “wife” signifies all programming-party-pooping, illogical things in the universe. Still, I persist. “It started as just an idea for the Nazis, too, you know.” The engineer makes a reply that sounds like a retch. “This is how I know you’re not a real techie,” he says.

"Debugging: what an odd word. As if "bugging" were the job of putting in bugs, and debugging the task of removing them. But no. The job of putting in bugs is called programming. A programmer writes some code and inevitably makes the mistakes that result in the malfunctions called bugs. Then, for some period of time, normally longer than the time it takes to design and write the code in the first place, the programmer tries to remove the mistakes."

I peered over at Morty, whom I'd clearly never seen before. This round old man in his empty store, for whom I'd never felt anything but pity, had just told me off in ways he could not imagine. He put it all together: Brian's networks, the bank vice president's universe of transactions, the software I write, the systems I install, the sexy bouts of software writing — all that was suddenly and clearly related to the world's financial center now all emptied of people. It's the modems: computing as a kind of neutron bomb, making all the people disappear, leaving the buildings.
In my world, it would be so easy to forget the empty downtowns. The whole profession encouraged us: stay here, alone, home by this nifty color monitor. Just click. Everything you want — it's just a click away. Everything in my world made me want to forget how — as landlord, as programmer, as landlord/programmer helping to unpeople buildings like my very own — I was implicated in the fate of Morty and the bag shop.