Book review: Learning Dojo
I usually don’t do technical book reviews unless 1) I’m specifically asked or 2) I really like the book. I do this to avoid putting up too many bad book reviews because there are so many bad technical books out there.Â When I was contacted about reviewing Learning Dojo, I warned them that I have a very high level of expectation for technical books given that I’m an author. The company, Packt Publishing, said that they were interested in my honest opinion and so here it is.
Another instance of inappropriate tone really got to me (p. 41):
This would in itself be kind of odd. I would really recommend to create your own widget when doing anything which will show up on the page as you get so much for free, but just for the sake of argument, let’s say that you don’t.
So he’s basically telling me to do something that he’d never recommend doing just “for the sake of argument?” What a waste of time. And don’t get me started about the run-on sentence.
Several other things really distract from learning Dojo. There is a constant shift in author voice, alternatingly referring to the reader as “you” and “we.” I really hate reading technical books that use “we,” but changing back and forth is very annoying.
The general format of the book was a bit rough. I’m not sure if it was a lack of editing, but I found grammatical errors abound. There were also some code snippets that were just flat out incomplete and looked to be formatted incorrectly. All of this, combined with the strange tone I mentioned earlier, made the book very hard to follow
Overall, I was very disappointed with this book. The first few chapters made me want to stop reading. Don’t get me wrong, I did learn about Dojo, but not at the pace and in the manner that would help me.
Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.