A technothriller for the malware and Stuxnet era
An airliner’s controls abruptly fail mid-flight over the Atlantic. An oil tanker runs aground in Japan when its navigational system suddenly stops dead. Hospitals everywhere have to abandon their computer databases when patients die after being administered incorrect dosages of their medicine. In the Midwest, a nuclear power plant nearly becomes the next Chernobyl when its cooling systems malfunction.
At first, these random computer failures seem like unrelated events. But Jeff Aiken, a former government analyst who quit in disgust after witnessing the gross errors that led up to 9/11, thinks otherwise. Jeff fears a more serious cyber terrorism attack targeting the United States computer infrastructure is already under way. And as other menacing computer malfunctions pop up around the world, some with deadly results, he realizes that there isn’t much time if he hopes to prevent an international catastrophe.
Written by a global authority on cyber security, Zero Day presents a chilling “what if” scenario that, in a world completely reliant on technology, is more than possible today - it’s a cataclysmic disaster just waiting to happen.
©2011 Mark Russinovich (P)2012 Macmillan Audio
I love to read and since 2011 I have been mostly listening to audiobooks because oftentimes there is nothing like a good narrator.
I've been looking for computer or Internet tech thriller but surprisingly in this Internet Age, there are surprisingly few. This nove so far is one of my favorites. I loved Daemon by Daniel Suarez and the sequel Freedom and when I finished them, I went looking for more. This Jeff Aiken Novel was what I found. I wasn't disappointed although I must add that it is hard following a book like Daemon so that says a lot for this author and this book.
I did like this better than Daemon in one respect, the author went into the tech details much more than I'm used to seeing in this small genre and for that I am glad. I can't say enough how much I enjoyed reading parts such as when our protagonist Jeff worked his way through the code on the machine at the law firm or how he describes how script kiddies use buffer overflow bugs to execute code. He explains it in such a way that you don't have to be a computer scientist to understand him. My wife confirmed that for me because she isn't a "computer person" as she puts it, while I am a system and network admin and we both enjoyed it equally.
One thing I'd like to note, because of what I said above and how he goes into detail regarding things like buffer overflows, etc; This is not a hacker instruction guide. You won't learn how to hack by reading this book. Sure, you might get a general idea or even come up with a decent flowchart on what and how to do certain things but I think Mark Russinovich does an awesome job going into the tech stuff while keeping the non-tech audience interested.
I also enjoy the author's writing style. It isn't so much a lyrical style as much as he explains things and tells the story in such a way that lets you concentrate on the story instead of reading or the listening. Even with audiobooks, I often find myself rewinding or playing parts over again because I just didn't get something. I didn't do that at all with this book, well....unless our dog jumped in my lap or pulled my pant leg wanting to go out. :)
Some of the worst written tripe I've ever bothered with. Horrible writing style, mediocre, magical story. A childish, sexist fantasized delusion, through and through.
...The author left a few too many things up to the reader to assume, rather than give explanations or confirm certain dots were connected. The ending also kinda fell flat on its face, it seemed unsatisfying and abrupt. I didn't have any problems with the narration as others have stated.
I thought the storytelling in his book was off topic and not very deep. I'm not sure I'd try another one of Mark's book's without a good recommendation.
Alien Out of the Shadows looks like fun.
I have not, I enjoyed his performance in this book though,.
Straight to DVD.
I thought the book focused far too much on the idea that assassins and violence would come into play in stopping the viruses. Could have used a lot deeper look into the "How" side of things. Instead, it reads more like "Super virus is released, and it works. Computer techs uses their skills to thwart and kill the perpetrators just in time to release signatures to virus vendors." Meh.
I picked up this book because the author is someone I highly respect from the tech world. The points are accurate and the author spices things up a bit. This book needs to be read on Kindle or paper. The narrator reads long stretches of Assembly language code. this turns into 5 minute monologs of hexadecimal figures and computer language that was never designed to be read aloud.
The ending was also anticlimactic and didn't fit entirely with the beginning of the book.
I still recommend reading this book. just do it on Kindle or paper.
I might as well try book 2...hoping for something better
Same. Character. Voices
Not sure why it was determined to say every part of the code in the book to the reader. Mr. Heller must have thought "this is ridiculous" Alot of characters came into the story. The voice narration never changed up much. Everything was about the Russians in the beginning. For instance..."Hey, who stole that bread!?" "Must be the Russians!" This book got boring fast.
Why does every nerd book have sex? Felt like the author was projecting something. Some parts of the book made no sense. It made no sense to the point I am going to listen to book 2 just to get the taste out of my mouth.
It is interesting to read about cybersecurity. Some of the first scenes were suspenseful. However, I think it is not a good idea to listen to this book in audio form since the narrator reads every character when reading a snippet of encrypted code, for instance...
Lose the opening sex scene. It's laughably bad. It's also unrelated to everything that follows. I can only guess that the editor told the author that the book needed more sex, so the author grafted on this clumsy scene.
A little bit of a letdown. It's hard to explain without revealing too much. Let's just say that I disagree with the author about how many systems would be patched.
It's competent and professional. He only had a few mispronounced words. The problem is, they were technical terms. It's a little jarring, and it suggests that he didn't always understand what he was reading. However, he did pronounce the majority of technical terms correctly, so his occasional mistake is forgivable.
My bigger complaint, and it's the reason I docked him one star, is that his voice is a bit harsh and grating. Not enough to make it difficult to listen to, but just enough that you wish somebody more melodious had this gig.
Not really. It wasn't compelling enough. It's a dime-a-dozen thriller. The only difference is that this is one of the few that gets the technology correct. We need more of those.
Report Inappropriate Content