Spring in Action (5e) has been a somewhat frustrating experience because I actually think that overall, the content is quite good for the topic. I feeSpring in Action (5e) has been a somewhat frustrating experience because I actually think that overall, the content is quite good for the topic. I feel like it does do a pretty good job of going over how a project could apply some of the different features of Spring while doing a decent job of also explaining said features.
The problems mostly lie in the typos and errors, both in the text itself and the sample code repository. If you're trying to follow along, there are parts that are straight up just not covered in the book but exist in the sample code. This means that the errata isn't being incorporated into the latest versions, including ebooks, which is disappointing. The other main issue I have with SiA5 is that it kind of meanders in areas where the author could have just focused on going more in-depth on one particular way of doing something.
I really would like to see the next version focus more on less because I actually like the idea of working on a project throughout the book, it's just too frustrating to do in its current form. Based on some other reviews of this edition, it's possible that the previous edition had better editing; I may take a look in the future and update this review if that's the case....more
Easily one of the best-written and most important books on Java. The format makes it great for both a reference book and for a book you can flip throuEasily one of the best-written and most important books on Java. The format makes it great for both a reference book and for a book you can flip through and pick out what you want to learn more about, and the abundant code samples make it really easy to pick out the context of the information....more
Clean Code took me a few months of on/off reading to get through. I think the first third of the book was a really easy read that made made clear whatClean Code took me a few months of on/off reading to get through. I think the first third of the book was a really easy read that made made clear what writing clean code means. Since the focus is mostly on putting out better code in Java, it helps to be familiar with the language, though I imagine newer C# developers might get something out of this book as well due to relative closeness of the two.
However, eventually the book feels like it's taking an incredibly long time to explain the same thing over and over again, and I just didn't feel as invested as I was when I first started to read it. There were a few interesting pieces of information in the latter half of the book, such as the Exception Handling chapter, but it just felt like I had to force my way through a lot of repetitive writing to get the good parts.
The main reason people should read Clean Code is to understand why Java code is written the way it is. When I first started using Java, I didn't really understand why it was written with extremely long and descriptive names for classes, methods, and properties, but going through this book makes it clear that this book is part of the reason it's still written that way today. If you are newer to Java or just want to understand the code style better, this is a must-read; others will probably find Clean Code a boring slog.
I think a revised and slimmed down version of the book would make for a much better experience. ...more
Loading...
