I rather liked this book, and learned a lot from it (far more than I have from a lot of other computer programming books). The things I liked about itI rather liked this book, and learned a lot from it (far more than I have from a lot of other computer programming books). The things I liked about it is:
1) While the concepts are demonstrated in .NET, there's references to other languages (Java and Ruby) and the concepts I imagine would transfer fairly easily. 2) The book is written almost as if you were talking to the author right there. It didn't feel as artificial as other books, and you can see there's 'personality' in parts of the book. 3) There's discussion of both technical skills, and soft skills. Part of his assumption is that you may need to try and influence the organization to do more testing.
There may have been example code out there, but I didn't notice it referenced. If there wasn't an example project that he wrote to demo the proper patterns he's talking about, then that's really the only thing I can think of that this book could use a good amount of improvement on.
I was reading this book right as I was beginning a new project, and really 'took to heart' a lot of stuff he said, and implemented tests following his guidelines. I'm confident to say, that in the short time it took me to go through this book (maybe a month) that the tests written in this project already saved me twice. If others are thinking of reading this book, I kinda recommend a similar idea..that being, work on a new project starting about half way through this book. It's nice to get pretty immediate feedback regarding how the concepts help....more
I really enjoyed this book. Some information is a little out-of-date, especially in the section regarding what comes next. Also, the metadata table thI really enjoyed this book. Some information is a little out-of-date, especially in the section regarding what comes next. Also, the metadata table that they mention also doesn't exist any more, either.
Overall, honestly I'd say this book is definitely worth reading to anyone who's into C#/Entity Framework. I found that this book really supplements the Pro ASP.NET MVC 4 book that I am also going through. There's quite a bit with the entity framework, and the Pro ASP.NET book simply didn't cover everything needed.
I rather enjoyed this book, especially given it's one of the best books on Linq I could find anywhere. This book is a little out of date, but it doesI rather enjoyed this book, especially given it's one of the best books on Linq I could find anywhere. This book is a little out of date, but it does a very good job of explaining how to use Linq. If you're a C#/VB programmer, and haven't been using Linq, then I really recommend looking into it. Linq makes your programming so much more readable and simplifies things a lot.
There are a few negatives about this book. The first, I already mentioned - and that's the idea that it's a little "out of date". The stuff described still works fine, but there's some tips about what's in current development in regard to Linq that are much more stable now than when the book was written and would make things much easier. For example, Linq to XSD is described much later in the book, much after Linq to XML. I would have wished to know about Linq to XSD a little sooner.
One area of the book I *highly* recommend skipping all together are the chapters in regard to Linq to SQL. While I did read it, this method of data querying isn't something you really want to do (well, maybe except in Linq Pad - which is something you should look into while reading this book). The Entity Framework is a much better way of doing the same thing that Linq to SQL does. Largely speaking, this section regarding Linq to SQL is kinda useless at this point. Instead, I'd look into "Programming Entity Framework" and "Programming Entity Framework: Code First" for more information regarding the Entity Framework. LinqPad also supports the Entity Framework.
Overall, I still think this book is quite good. It definitely shows how powerful Linq can be, and how you can use it in a lot of different situations. Also useful is the last chapter regarding what's being developed. While this information is a bit out of date, it definitely sparked my curiosity with Dryad Linq, which is something I want to look into next....more