Alas. So, a lot of details get left out whenever you tell a story. That's the price of telling a story. Narrative is as much about what you don't tell as what you do. I GET THAT. But at the same time, when the wrong details are left out, I can find narratives just ... unacceptable. And that happened really fast with this book. He retells the Mat Honan saga, and fails to describe how quickly (under a month), comprehensively (he only lost applications and settings, no photos, no movies, etc.) and inexpensively (under $2K all-in, as near as I could tell) Honan was able to recover from a really comprehensive hack. Obvs, when you are living through what Honan lived through, your life is hell. But I could tell you this story about W.B. from when he was staff at UW and I was an undergrad and his account got nuked and all the files became available storage space and he wound up having to do _by hand_ the kind of recovery that Honan was able to hire done. And what W.B. lost was about a hundred thousand words of a non-fiction book he'd been working on for years. No backup. No printed draft. Nothing. It took him a really long time, so I calibrate pretty much every data loss story against W.B.
In fact, as near as I can tell, Honan's loss is presented as permanent. Which puts just a completely different spin on the tale. I don't feel like fact checking everything else that appears in this book, so I'm gonna delete the sample and forget I ever took a look at this thing. If you know, from having read the book, that Honan appears later in the book and the recovery is presented, let me know and I'll give it another shot.
Oh, you want Honan linkage? Okay:
I remembered the coverage from reading it when it was all exciting and new, and I remembered his recovery being so comprehensive and quick (and I know it felt really expensive, but again, it's all about calibration). I pulled the links to make sure I didn't imagine what I remembered. And I didn't.