It is best to be the CEO; it is satisfactory to be an early employee, maybe the fifth or sixth or perhaps the tenth. Alternately, one may become an engineer devising precious algorithms in the cloisters of Google and its like. Otherwise, one becomes a mere employee. A coder of websites at Facebook is no one in particular. A manager at Microsoft is no one. A person (think woman) working in customer relations is a particular type of no one, banished to the bottom, as always, for having spoken directly to a non-technical human being. All these and others are ways for strivers to fall by the wayside — as the startup culture sees it — while their betters race ahead of them. Those left behind may see themselves as ordinary, even failures.

There, in that presumed paradise, the engineers were stranded in the company of an infantile mentality. They created artificial smartness, made a simulacrum of intelligence. But what they talked to all day was little more than a mechanism that read bits off a disk drive. If a comma in the code was out of place, it complained like a kid who won’t tolerate a pea touching the mashed potatoes. And, exhausted though the programmer may be, the machine was like an uncanny child that never got tired. There was Karl and the rest of the team, fitting the general definition of the modern software engineer: a man left alone all day with a cranky, illiterate thing, which he must somehow make grow up. It was an odd and satisfying gender revenge.

Is it any surprise that these isolated men need relief, seek company, hook up

This is not to say that women are not capable of engineering’s male-like isolation. Until I became a programmer, I didn’t thoroughly understand the usefulness of such isolation: the silence, the reduction of life to thought and form; for example, going off to a dark room to work on a program when relations with people get difficult. I’m perfectly capable of this isolation. I first noticed it during the visit of a particularly tiresome guest. All I could think was: There’s that bug waiting for me, I really should go find that bug.

Yet, when we allow complexity to be hidden and handled for us, we should at least notice what we are giving up. We risk becoming users of components, handlers of black boxes that do not open or don’t seem worth opening. We risk becoming people who cannot really fix things, who can only swap components, work with mechanisms we can use but do not understand in crucial ways. This not-knowing is fine while everything works as we expected. But when something breaks or goes wrong or needs fundamental change, what will we do except stand helpless in the face of our own creations