How to describe my fascination with Ellen Ullman's 2003 novel The Bug? The scene is Silicon Valley in 1984 when the mouse as an input device is still an innovative new technology. The story is told from the perspective of software developer Ethan and a tester Berta--both doing battle (often at cross purposes) to track down an insidiously elusive bug they end up calling "The Jester." The bug takes on a personality of its own, appearing only intermittently at the worst possible times, sabotaging important demos, and ultimately becoming a haunting nemesis for both of them. In the end, Ethan's efforts to debug his code become intertwined with his efforts to debug his life, which is rapidly unravelling all around him as he loses his wife, colleague, and the manager who appreciated him and lured him into the project to begin with despite Ethan's self doubt.
Ethan's real passion is an artificial intelligence program he calls the simulation in which he tries to program his cyber creatures to socialize and thrive. Survival in the simulation depends on whether a cell is surrounded with other healthy cells, but Ethan's creations are not thriving, despite his efforts. The novel's structure is divided into four parts, each preceded with a diagram from the simulation, showing the progression as a hapless cell is deprived of each of its neighbors in turn, paralleling Ethan's own life of increasing isolation.
The author was an English major before she got into high tech (I can relate to that) and weaves a number of literary allusions into the novel including Eliot's Middlemarch, Kafka's The Metamorphosis and Shelley's Frankenstein (the tester's name is Roberta Walton and the name of the narrator in Frankenstein was Robert Walton).
Ullman's descriptions of software engineers and their quirks absolutely rang true from my own experiences in the industry of the 80's--from the relentless fascination with puns to the office collections of toys like squirt guns and boffo swords, to the hilarious description of Ethan's attempts to answer pointed questions from the bean counters about The Schedule while balanced precariously on the only seat remaining in his manager's office--a bouncy ball.
The toys and puns take on a vaguely hostile air as the intense pressure from the venture capitalists to deliver on the impossible schedule increases. Ullman vividly describes the 7x24 obsession with churning out and debugging huge quantities of code and the challenges many technically brilliant engineers have with emotional intelligence and deciphering what is really going on in their bewildering social interactions. She also does a great job of depicting the challenges of management, aka herding the cats--both what an excellent manager can mean to the productivity and sanity of technical people as well as what havoc can be wrought by a terrible manager. She shows rather than tells us these things--with dark humor and clarity. The story does take a very bleak turn at the end, but she has lined up all the events that lead to this so thoroughly that the ending is logical and inevitable.
Ullman also penned a 1997 autobiography called "Close to the Machine: Technophilia and Its Discontents," about her Silicon Valley years as a software developer--she mentions that she was the first engineer to be hired at Sybase to work on the client side of groundbreaking client-server architecture. In "The Bug" the company is called "Intelligentsia" but includes an eerily accurate portrayal of one of Sybase's founders and his habit of nodding and smiling during every conversation regardless of the content.
Other novels have explored the computer world and its sometimes cutthroat ruthlessness. There aren't many novels that delve into the complexity of a coder's brain, motivations and inner life with this level of depth and empathy. To unambiguously tell the machine what it is you want it to do, you often must become part machine yourself--sometimes at great cost.
