As The Wife probably knows more than most, I read a lot of books. That is, books about technology, mind you. I think I took a SQL Server 2000 book on my honeymoon. The Wife reads more (approximately 2.5 vertical feet of books per month) than I do, but she's all over the chart with bios, mysteries, thrillers, oddities like a book about the number zero or salt; even those sappy romance books.
I'm currently reading what could be a really interesting tech book but I feel more like a proof reader. I'm not saying I'm like Chris Sells or anything with my own book, I've got some errata. However, this book I'm reading now has ascended the six stages of book errors with invalid code and sentence struggles in short order:
- Whoops
- Laughter (with)
- Laughter (at)
- The 'oh crap' stage
- Can I learn anything here?
- Is this book actually hurting my brain?
I've never seen one this bad before. It really makes me appreciate the great editors that I was fortunate enough to have on my team. This is more of a reminder to myself - for gosh sakes, proof your work before you send it out! Gah!
Footnote - any grammar issues in this post were purely intentional.