by Mike Snell, Bruce Johnson, Brian C. Lanham, Sara Morgan, Shawn Wildermuth
Despite the snappy title, I actually found the book generally pretty good, but some chapters were definitely better than others. A few, I felt, were very good, such as requirements gathering and use cases, modelling the application, and so on – but many of the later chapters were less useful. There seemed to be an inverse relationship between how many code examples there were, and how good a chapter was. I think that the chapters with little code assumed that if you were through to doing the MCPD exam, you can probably work the code out for yourself, or perhaps that the presence of code examples showed a move away from considering the design bit of ‘Design and Developing…’
That said, the exam didn’t really match up with my expectations, or what was covered in the book. If anything, the exam seemed to be about a lot of the stuff I’d covered previously in the MCTS exams. So neither really hit exactly what I felt I should’ve been examined on, and the book and exam didn’t really cover the same areas. And there are probably better books out there for covering development generally.