Alright, fighting a little frustration here. My weekend is devoted to 2 chapters of this book as well as another article for <a href=”http://www.communitymx.com”>CMX</a>. However, the point of this post is that I’m trying to fight disillusionment here. I’ve found some tech books either rehash the documentation with tutorials in a pretty cover, simply rehash the docs and make corrections, or ignore them altogether (for good or ill). Well, I don’t know how my editor feels, but this is some bs. I am NOT going to rehash the documentation. If people buy this book, I want them to learn something they couldn’t read in the documentation. I think the book is supposed to be all inclusive, but to me, why? I’ll find out Monday, I’m sure, but in the meantime, I’m just going to rehash the docs only where I think something needs to be included. Everything else, you can read in the docs. I refuse to add content strictly for the sake of adding content. I don’t think that’s fair to my readers.
…am I wrong? Is this what your supposed to do in a technical book? Rehash the docs? If so, I’m deviating from the norm, period.