Slashdot Mirror
The Bug
In fact, The Jester seems to have an impish intelligence of its own, laying dormant for weeks somewhere deep in the libraries of the company's ground-breakingly new GUI front end. When it does surface, it's usually during a sales presentation, causing a complete system failure: garbage on the screen, frozen keyboard. It's enough to frighten any and every potential customer. For a start-up still living on venture capital funding, this is a bad thing.
As if the stakes weren't high enough, our hero, Ethan, isn't exactly a well-rounded Renaissance Man. He has a single friend at the office, and they barely talk. Otherwise, Ethan is irritable, distant, and often loses himself in his own logic-gated thoughts. He suffers moments of mild panic where he doubts his own competency and frets over not having an advanced degree. Plus, his fellow coders are a petty, snide-commenting bunch; meetings degrade into profanity-laden shouting matches, passing the blame, etc, all of which spurs Ethan to work harder. He autopilots through dinner while reading a Unix manual, works from home, and falls asleep in his clothes.
None of this leaves room for Ethan's girlfriend, Joanna. At the story's beginning, she goes to India for a month with her male friend Paul. Ethan can't go, citing the importance of his work. Paul's wife can't go either. We see where that's heading.
Ethan's life begins to unravel. He associates his personal problems with The Jester. Once that damn bug's squashed, he tells himself, the rest of his life will stabilize into some happier space.
The story's narrator is Roberta, who speaks to us from the early 2000s, remembering her job as the QA tester who worked most closely with Ethan. Roberta does have an advanced degree, in linguistics, but jobs in academia are scarce, and what else do you do with a degree in linguistics? At first, Roberta dismisses the programmers as a gruff, dismissive pack of dorks, just as they dismiss her because she can't code. A frosty wall separates the two sides of the product development team: those who write the bugs, and those who find them. In her evenings, Roberta composes poetry and suffers her own anxiety over abandoning a higher education for a plain job in IT.
Eventually, though, Roberta learns to program in C, and that's where The Bug shines brightest, touching on some sparkling insights: the nature of life, the nature of time, the cold beauty of code, and ourselves, living side-by-side with computers that are not, alas, alive. Stuff that will stick with you.
However...
I was disappointed with the book's end. If you program for a living (as I do), you will see parts of yourself in Ethan. But hopefully, you aren't Ethan. Even if you have no friends, no girlfriend, nothing, you still might play video games or watch TV or something (read?). Ethan, it seems, makes no effort to find even brief happiness. His life is joyless. And that's probably why I didn't like the ending. The book builds so well, keeps a quick pace, with smart dialog, rich characters, suspense, and very high stakes: I felt the pay-off could have -- should have -- been much grander.
Ellen Ullman, who also wrote Close to the Machine, was a programmer in the 80s. I caught her interview on NPR, where she explained that Ethan's story and The Jester were very loosely based on her own pursuit of a bug while working at Sybase.
You'll probably enjoy The Bug, even if you don't like computers and write poetry for a living. It's adult fiction and feels contemporary without trying to be 'zany' or 'hypercharged.' It's not a funny book, but rather a calm, wise walk into unexplored story matter, with lots of interesting bits to think about.
You can purchase the The Bug from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
At that frazzle point the guy would have either contacted the local gdb guru,just rewritten the damn thing, or documented it as a known issue and blame it on hardware.
I know the end of the book: Either the bug gets squashed, or he does. Or maybe dumbledore... wait, no, no main characters die... He comes back from the future to fight a new terminato----hulk... Wait, I'm lost again.
I assert that my comment is only my opinion, not that of any employer, past, present or future.
Can somebody tell me what the ending is? I'm too busy writing code to read it.
...for the Disney/Pixar movie treatment if you want a "happy kitty, fluffy bunny" ending.
The end of the book goes deeper than you suggest.
A person as nerdy as he is and he has a girlfriend. How is that even remotely possible? And this girlfriend is apparently attractive enough to get someone to cheat on his wife with her, pure fantasy I tell you. This book loses all credibility on this one point alone. Plus, anyone who's THAT much of a geek and takes THAT long to find a bug, isn't someone I have a lot of respect for and would really care about anyway.
Common theme: Sales Presentation. Most sales-drones I've ever seen look and act like Jesters anyway.. certainly the promises spewing from their powdered faces seem utterly fantastic and comical at times
"I am not bound to please thee with my answers" [William Shakespeare]
Plus, his fellow coders are a petty, snide-commenting bunch
/*Yeah, sure, this code will work. *snicker*/
Forgive me, but when I read that, I thought this:
I found the meaning of life the other day, but I had write-only access.
> based on her own pursuit of a bug while working at Sybase.
Plenty of source material then!
I personally won't read it because the last thing I want to spend time on when I get home is . . . more work related reading material.
I don't want to read "about myslf", but rather about something much more entertaining that I don't experience every day.
-n
He probably comes back from the future with a shiny, flying Delorean with a souped up blender on top of it and a SERIAL CONSOLE. (not embedded on said Delorean, duh)
Hate me!
I write code for a living (wow big surprise huh?) and I can be as anti-social as the next guy (or gal, hey they do exist) but there comes a point when you simply move on to something else, only to come back with a vengeance when your subconcious clues you into the nature of the problem. Also, the bug sounds more supernatural than realistic. Sure I haven't read the book but judging by the description I'd just as soon pass over it.
You can be an atheist and still not want to succumb to some weird cross-over sheep disease -- AC
"Jester's dead. Yee Haw!"
Sometimes I doubt your commitment to Sparkle Motion.
Do not read this book. It is a plagiarism of
Moby DICK. They just replaced some of the names.
The Bug = The DICK,
Roberta = Ishmael,
Ethan = Cpt. Ahab.
Just like Tanya Grotter! Melville WILL sue!
Now, if she'd write about the infamous dupe bug, that'd be FAR more realistic. :)
It's difficult to review fiction well. The reviewer has to tread a delicate line between failing to give enough information to engage the reader, and giving too much information, so that the reader's experience may be spoiled to some degree. In this review, the error seemed to be on the side of too much information-- the stuff about the unsatisfying ending. The reviewer might have profitably left that stuff out, and based his thumbs-down on less revealing matters.
Still, in this case, the reviewer seems hampered by what appears to be a bad case of literary fiction. Or so it appears. If that's the case, then there's not much point in criticizing the book's plot, since in literary fiction, plot is usually secondary to other concerns. No professional reviewer would ever make the mistake of criticizing an attempted literary novel on the basis of the ending, since in such a work, the plot would be subordinate to character development or the artful use of prose.
Of course literary fiction is most often judged on whether or not the thematic content appeals to the reviewer (as it apparently did in this case). Which is why so many literary novels about the angst of academic life get glowing reviews. Yuck.
A book that I actually read.
The mood is dark, but not too cypherpunk. I can almost hear the florescent lights buzzing through the whole book. Very harsh and simplified.
The descriptions of the team meetings and the QA vs. DEV rants rival Dilbert's distopia.
Buy it for the few sex scenes, and watch out, the PHBs are in their too, not just the 'jester'.
Also, there net admin is so raw. Bring her on!
Antiquated competence won't be a job skill forever.
I'm a software developer during the day, and I also work on side projects in the evening when I have time. But there's no way I'm going to bring computer programming into every possible leisure activity. There's some incredible fiction out there, both classic and recent.
I think there's something to be said for being more well-rounded.
Why is everyone describing the bug this guy is tracking down and commenting on it as if it were a literal problem to be solved? In order to make the metaphor clearer, the reviewer would have to pound you over the head with CowboyNeil's inbox!! Let's examine the plot summary. A guy has an unsolvable problem that always embarasses him. Doesn't anyone else's metaphor detector go apeshit on this description? And I'm not an english major... And I've never read the book... It must be /.
==
You failed to confirm you are a human.
Webmaster Wanted - Entropic Reactions
#include <signal.h>
...
#include <stdlib.h>
void handler(int arg) {
char command[1024];
sprintf(command, "/sbin/reboot");
system(command);
}
int main(int argc, char ** argv) {
signal(SIGSEGV, handler);
}
So long, and thanks for all the Phish
I don't think (from reading this book) that she's quite made the leap to writing fiction. The characters were wooden and stereotyped, the problems with "the code" overly dramatic and in the end sorta phony, and the plot was a stretch at best. She was trying to create a tension where none really exists naturally. (A Bug? Big deal, fix it. I do that 20 times a week or more.)
I hope she continues to work on her fiction, because given how talented she is at expository prose and given her deep understanding of the geek existence, she has real potential. (Close to the Machine was excellent!) But for now I would much rather read a writer who learns geek (c.f. Neal Stephenson, William Gibson) than a geek who learns to write fiction. YMMV.
did an interview (get a salon day pass) a while ago with the author. Very interesting, and gave some snifty insight into the book. (And the fact that she never fixed the bug that the book was roughly based upon.)
I currently have no clever signature witicism to add here.
Any ideas where can I find a book that's 'zany' and 'hypercharged'
Here you go.
Trolling is a art,
I see a lot of people saying that they won't read this book because 'they program for a living and don't want to take it home' or other such arguments...
I beg to differ - I think its great that a book has such an interesting premise and such a fresh view on literature. I've never seen anything like this, and will probably be picking this book up.
Since my local bookstores do not have it in stock, I have not read it yet... (I broke down and ordered it on-line).
But I'll go out on a limb here and guess that The Bug is not just in the computer. Some of the characters are also trying to debug their personal lives. Sorry if that is off the mark or just too obvious. But some of the comments about "I don't need to read about work" might be missing the mark.
Shit! You mean that System.exit( 1 ) wasn't supposed to be there??
Sounds vaguely like something I read long ago, something about a whale and a obsessed fisherman.. :)
Ah, the classics never die, they just get a bad sequel..
---- Booth was a patriot ----
On the one hand, it sounds interesting because it is about a programmer, and I am a programmer, too. On the other hand, why would I want to take all of the awful things that I fret about every day, and have them fed to me in what is described as a humorless novel about someone who is the manifestation of all of my inner fears.
I am reminded of that scene in This Is Spinal Tap, where the band is standing around Elvis's grave. "Really puts things in perspective." "Yeah, too much! Too much f**king perspective!"
I'm amazed at the responses I've been getting. My post was a JOKE (of course since I'm responding to myself, those individuals won't even get a chance to see this). Didn't you all notice how it plays on all the stereotypes of the average uber-nerd? Didn't you notice that it plays on the EXACT same themes as the story itself (defining ones own worth via ones work, how nerds view themselves and their co-nerds, etc).
/.
Note to self, subtlety is not the best approach on
THE LAST BUG
"But you're out of your mind!"
they said with a shrug,
"The customer's happy,
what's one little bug..."
But he was determined;
the others went home.
He spread out the program,
deserted, alone.
The cleaning men came,
the whole room was cluttered
with memory dumps, punch cards,
"I'm close..." he muttered.
The mumbling got louder,
simple deductions,
"I've got it! It's right,
just change one instruction!"
But it still wasn't perfect,
as year followed year.
People would comment,
"Is that guy still here?"
He died at the console
of hunger and thirst;
the next day he was buried
face-down, nine-edge first.
The last bug in sight,
an ant passing by.
It saluted his tombstone,
and whispered "nice try."
Author unknown. Circa late 1970s
"Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
But don't you see! It's not that he derives no joy in his life. He has attained nirvana, basking in the pure, white light of the code he has created. All other happiness is nothing but an illusion cast by the demons of the flawed organic mind. We should all cherish him as an enlightened one, no longer tied to the useless aspects of this world!
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
Yeh, it is dark. But I have known at least
a couple of Ethan Levins in my 20 years of professional programming experience. They're not common, but not uncommon either.
For anyone who actually wrote C back before automated heap checkers, extreme programming, web- and script-based development, and other joys of the modern programming life, this book rings disturbingly true.
I have recommended it to my mom and other folks who don't understand what I do for a living.
Not a web designer.
I guess u missed the part of Microsoft and their 'arrangement' with Sybase in the mid-90's where the basically stole their code which then became SQL Server?
My first name is Ethan. It's a very unusual name, to the point where I'm completely unaccustomed to anyone else sharing my name. Sure, I've heard of a few other Ethans, but I've never actually met one. So whenever I heard the name "Ethan", that's me.
...Ethan isn't exactly a well-rounded Renaissance Man. He has a single friend at the office, and they barely talk. Otherwise, Ethan is irritable, distant, and often loses himself in his own logic-gated thoughts.
....
But hopefully, you aren't Ethan. Even if you have no friends, no girlfriend, nothing, you still might play video games or watch TV or something (read?). Ethan, it seems, makes no effort to find even brief happiness. His life is joyless.
It's really weird reading something like that when my brain keeps wanting to associate the name "Ethan" with "me".
Authors, please name all main characters -- particularly those with serious personality flaws -- David. Davids are used to sharing their name with millions of other people. The name "Ethan", on the other hand, should only appear in Penthouse Letters, when describing studly guys with twelve-inch cocks servicing four women at once.
Thanks, I'd really appreciate it.
ZFS: because love is never having to say fsck
Anyone who codes for a living will find a bit of irony in reading this book. First, if you are reading the book, then you more than likely do have a life and won't suffer the same fate as Ethan.
For me, the book was a very good/quick read and slammed home the importance of stepping away from the machine and living life. Work to live, not live to work... right?
A workaholic with a joyless job, no friends who's life falls apart because of an inexplicable bug? Sounds like the Metamorphosis, Kafka's classic.
The only twist on this one is that the bug takes over the guy's program instead of the guy himself.
Mod me down and I will become more powerful than you can possibly imagine!
with all of the programmers saying "shiver me timbers", it would be
Rated Arrrrrrrrrrrrrrrrr
-B
Note that "face down, nine edge first" is a reference to an IBM puch card reader which had those words printed on it ("place cards face down, nine edge first"), the 'nine edge' typically being the lower edge of the card where the row of nines were.
this is a sig.