Slashdot Mirror
Masters of Doom
Virtual reality was the craze of the time, and Doom offered a glimpse into what it was all about. But this innovative game did not come from any of the "big" video game developers of the time, and it was not the built by a large team with huge resources. Although it was the product of many people's efforts, it was primarily the creative genius of two people, both named John.
John Carmack and John Romero are names that every self-respecting Slashdot reader knows. Carmack even posts here occasionally (hi John!). Until I read this book, I knew very little about the personal life of Carmack, and I thought I probably knew too much about Romero. Like many, I have been intrigued by their successes (and failures), and was interested in learning more about what makes them tick.
Masters of Doom starts off with a chapter for each John, telling stories from their childhood that made me realize they were just typical American kids, with the same kind of problems that many of us probably had. These are important chapters, and the author repeatedly references these stories throughout the book. Although the book chronologically covers the entire lives of the two Johns, most of the book details their working years, from their time at Softdisk until now.
This is where the book was most interesting to me. The details of the camaraderie that existed among the team made me feel like I was there. The author got a lot of his information from personal interviews with people, and it really shows in his writing style. First-person accounts are woven together so you get to know what each person was thinking while the story plays out. For instance when the id team met with Sierra On-Line in 1992, you get first-person impressions from both sides of the meeting, giving the reader a lot of insight that you would ordinarily never get.
For me, the book's climax was during the initial releases of Doom, when huge checks were pouring in. Things were going really well for the team at this point, and the book describes things like John C. and John R. dropping off a check for five million dollars at the bank's drive-through, while riding in one of their Ferraris. Although things were looking great for the team at this time, the future really held turmoil and disappointment.
The only negative comment I have about this book is not really a criticism of the book itself, or even the author. I believe the story was accurate, and while it didn't have any shocking new information, it left me feeling sad to see such a powerful combination of talent break apart because of personality conflict, and sad at the thought that Carmack seemed to be losing interest in id Software. The book does mention Carmack's current interests in rocketry (which are even more exciting to me than his games), and Romero seems to have settled into a life he is enjoying, but the mood of the book seemed very depressing to me in the end.
Anyone who is a gamer or a self-taught programmer like Carmack and Romero would enjoy this book. The book does not require the reader to know much about games or computer programming, but I suspect it might be uninteresting to people who aren't either gamers or interested in computers. To the average Slashdot reader though, I would definitely recommend this book.
You can purchase Masters of Doom from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
ah yes the good 'ol days, playing "Ultimate Doom" and "Heretic" on a 28.8 dialup. I miss those days :( Now you have to worry about some kidiot with an aimbot and wallhacks getting ready to AWP your ass through wall.
Pls No Negative Modding!
While this book was a nice read for me, it would have been terrible for most. It was written very poorly. The only thing that kept me going was learning all the little things about the people who created doom that I didn't know before. I struggled through some parts of it, and was almost embaressed by others. Great read for those who are interested in the subject, but for people who have a passing interest.. I suggest looking elesewhere.
Paint.NET, a Free Image Editor, with Source Code Available!
is that first person shooters after Doom were called "doom like" instead of "Wolfenstein3D like."
I suppose "doom" is easier to say, but it doesn't give credit to the real first, the one that opened the floodgates.
Stupid sexy Flanders.
When I was in High School my teacher knew some people over at ID and we got to alpha and beta test Doom in computer club. I remember the still monsters and walls you would fall through and the numerous crashes we would have. Even then the game was a total blast.
I don't recall Commander Keen being cutting edge. Maybe in the PC world where scrolling was an issue. To me it seemed like a fairly second rate platform game compared with what I'd come to expect from other platforms over the preceding yeard. Talking of scrolling... I wish I could find my copy of Xenon II Megablast. I wonder if it will run at the correct speed on my more modern hardware.
John Carmack and John Romero are names that every self-respecting Slashdot reader knows.
I'm having trouble understanding everything after the 'every' and before the 'knows.'
I feel so dirty posting this.
I don't think that it is surprising that beloved games like DOOM are the product of the vision of a small group of people.
Games that really do engage us, do so at a very primal level. There is something about the game that has to click, and release your anandamides ... This syncronization of what you feel when you play the game and what the developer wanted you to feel is more pure, like it is in art, when this vicarious "anandamide" is personal ... so personal that it becomes universal ....
Corporations with big departments will create a lot of good games, but I believe the purity of the intensely personal experience can come only when the vision is personal, and concentrated in a few people rather than diffused ...
To see a world in a grain of sand, and then to step back and see the beach where the sand lies
Noone ever made a game called Daikatana. Quake 3 Arena was pulled before release when it was decided that it was just a cheap cash grab! RTCW was released without crippling bugs that made it unplayable on Radeon cards, and Doom 3 runs on mainstream hardware and was released in the first quarter of 2003.
The Johns stay together, get married, and live happily ever after!
The End.
I don't need no instructions to know how to rock!!!!
28.8 dial up? You call that the Good ol' days? You little whippersnappers don't know nothin' about the good ol' days.
When I was your age, all we had was seven computers in the whole world, five of them were in Nigeria, and they were connected by old loops of string. Instead of packets, you had to put a color coded ribbon on it and pull the string for 60 hours until the ribbon got to the other guy. Then he had to manually enter the data into his computer via punchcards and smoke signals, and we liked it that way!
We didn't have no fancy 3D engines, or even 2D, all we had was 1 dimensional games, lines with broken spaces in between and you had to pretend the long ones were space cowboys and the short ones were mutant trolls. It took 84 hours of processing time to draw 1 pixel, and we liked it that way!
You spoiled bratts and your instant messaging eDoom 7.0++ with real time anti-aliased bitmaps don't know nuthin about the good ol' days.
---
WARNING:Slashdot karma not redeemable in the afterlife.
Enter the latest in Trolling techniques: "It's cheaper at Amazon!"
I guess the best reply is:
"You must be new here! We don't buy from Amazon."
Obviously you have never seen the movie "Gigli" .
IDKFA
I am the master of doom.
0110100100100000011000010110110100100000011000100
For instance, you would use less flower in the next batch of brownies
I make my brownies with flour. Yours must taste pretty funny. Do you use the stems too?
Apparently grammar nazis don't pay attention to such trivialities as homophones.
I used to do DOOM I and II technical support. id outsourced it to a Colorado company called StarPak. For the first few days, I was doing the support practically alone, along with hundreds of other products with different companies. I'm proud to have recieved the first phone calls.
id provided an excellent knowledge base, and we were able to solve 90% of the problems people called in with. I felt really good enabling thousands of people to play this game - back then, everybody wanted to play it due to it's explosion of popularity and controversy, and people knew little about computers, just like today, with the difference that they were dealing with DOS and Win31, which was even harder for them.
I'll never forget the many times I heard kids scream "hooray!" in the background after I spent an hour on the phone with a very tired mother or father trying to make it work.
I believe that I received the first phone call ever of someone reporting motion sickness as a result of playing a video game due to the realism of 3D movement, since DOOM was the first game that had "bobbing". id thankfully had the insight to provide a switch to turn that off.
Another interesting call I recieved was from a guy who claimed to have produced (or maybe directed?) My Cousin Vinny, and said he wanted to make a movie out of DOOM. I put him in touch with id, and I'm glad nothing ever came from it. It would have made a crappy movie - the plot was a razor thin excuse to provide a setting for thousands of monsters to attack you relentlessly.
I also simultaneously operated on the 900 Hint Line. People would call up and ask the location of a particular key on a particular map. If you recall, the location of secrets was different between single player and multiplayer. We were encouraged to play the game while we worked (research! bwhaha!) and we always played multiplayer of course.
People thought it was amazing that me and my colleagues could rattle off the location of a secret on a map in single player mode while simultaneously playing multiplayer on a totally different map, all without checking the book.
Ahh, good times.
# Erik
http://www.gnu.org/philosophy/amazon.html