Top critical review
Better used as a doorstop
on 10 August 2017
The more I read of this book the more problems I find. Firstly it seems like there is a hell of a lot of fluff designed to make it have an impressive doorstop heft that could easily be cut. Do I really need to know so much history about the problems that led to particular design choices in C#? Basically no, I'd rather get to the meat of the solution. Which brings me to another problem - you often find that the author walks through all kinds of circuitous permutations before arriving at a point of saying something along the lines of 'of course, C# has far easier ways to do that now. Here's how..'. Why not just tell me the easy way first and leave the rest as historical background?! I'm sure that for all of these I don't need to know x older ways of doing something that have now been superceded. At least tell me the newest, simplest way first and then leave me to read about the older, crumbier way if I choose.
Worse than above is that there are mistakes - which in a coding book is pretty unforgiveable. I buy a book like this because I want to have a single comprehensive resource that is correct - and when that turns out not to be the case it means I can waste minutes thinking I am being thick when in fact there are mistakes that should never have got through to a published book. And so I go to look for errata on the Apress website - and there is none to be found!
Also the coding samples are sometimes missing or don't match the book.
I could go on but you get the picture. Crumby book I think.