My first bad book review
I got my first bad book review on Amazon.
It doesn't bother me that much aside from the fact that the author is clearly not even remotely a part of the target audience. I see that quite a bit in Amazon reviews. I remember one ages ago, I think for one of Alex Homer's books, where the reviewer went on and on about how the book doesn't tell you about this or that, and it was a beginner book! I've always been a fan of his writing style, and if it wasn't for him I don't know if I would've ever started coding again.
Fortunately the feedback I've been getting via e-mail has been pretty good. A guy from Spain, despite an apology about having poor English skills (apparently he's never seen teen chat-speak by American kids?), simply said, "I get it now." That's the greatest compliment I could ever get, because that was always the intention of the book.
Now that I've been away from it for awhile, I think the one thing I would do differently is perhaps do another example chapter that applies basic OO concepts. I went with the data access/container object example because the thing I've seen more than anything in bad code is repetitive data access, though I'm kind of a hypocrite because I rarely combine data access and some kind of object representing the data into one thing anymore. Then again, perhaps that's a natural progression for a learning developer. It certainly was for me.