3 ms·
Reasonable concerns, but most apply to print books as well. Reputation is reputation, whether it's a publishing house or a sole author. I've bought crappy bo
by jamesbritt 17y ago
Reasonable concerns, but most apply to print books as well.
Reputation is reputation, whether it's a publishing house or a sole author. I've bought crappy books from reputable publishers (O'Reilly had a book on VBScript that was total crap, for example), so you still have to do some checking to see if a book is really going to be worth your time and money. For most technical data it seems a bit of time on Google should tell you if the author knows his or her stuff.
A more reasonable concern is copy editing. While publishers may no longer be vetting the technical aspects well as they should (The book RESTful Web Services, for example, has assorted (mostly minor) technical errors) the overall editing quality tends to be good. I have less faith in sole author/editor/publisher set-ups to have proper grammar and consistent use of the author's voice, for example.
OTOH, most E-books tend to be cheaper than printed books, and are often bought to expedite some development process. If I can save myself an hour two of research and dead-ends while working on a paid contract, then I've easily saved myself many times the cost of the book.
Finally, printed books go on sale, too, or end up in the discount bin, so while it's not the same as finding out you could have gotten something for free, it's close.
The value of technical info depends on how timely it is; these are perishable goods with a limited shelf life. You want it fresh, you gots to pay more.
One annoyance with E-books that wasn't mentioned was the lack of appropriate screen formatting. I have some PDFs from Pragmatic Press, for example, and they are all laid out for the printed page, not for my laptop screen. Nothing flows; I have to deal with hard page breaks as if I were dealing with paper.