When I am Confused, I Shall Blame the Author

When a newbie is confused or can't get something to work, he blames himself. When an experienced developer encounters a problem, he blames the software. When an O'Reilly reader can't get something to work, he blames the documentation.



That's all right. As an editor and author for O'Reilly, I think our readers should expect no less than excellent documentation. That means covering the software both in theory and practice, warts and all. In my favorite review of ActionScript: The Definitive Guide, the reader writes "I have realised [sic] an important philosophical truism: From now on whenever I fail to understand something, I should blame the author and find a better book! "



Many authors are technically competent abysmal as writers. Many publishers and editors don't devote the resources or time to turn a so-so manuscript into a great book. I'm thankful to have worked with Colin Moock on my first book as an editor. If I edit 100 books, I doubt I'll ever work with an author as technically skilled, motivated, and personable as Colin.



Get your Daily Bruce!

What is your favorite computer book and why?