If you bought this, then you've wasted money, regardless of your level of expertise.
If you're a novice who's just starting out or a developer who wantIf you bought this, then you've wasted money, regardless of your level of expertise.
If you're a novice who's just starting out or a developer who wants to find out more about best practices, find books that target the areas you're looking to improve on; they will be way more useful by providing concrete and specific examples.
If you're an expert looking for a refresher, just about any software development blogs, sites, or forums that you've been following (you are doing this, right?) will give you better value.
The 97 things are each told in a max of 2 pages - very little room for anything more than a generic discussion. They range from common sense and popular practices to technical challenges and domain expertise. I doubt any professional developer would find even half of these immediately relevant and applicable to their current work/role. They just cover too many areas in too few details.
I'm not saying the advice is bad (although I did find myself shaking my head at a couple), most are good valid advice - I'm just saying this is a poor way to acquire them....more
This is a book that one could get started on the idea of "good code" - clean, readable, elegant, simple, easy-to-test, etc. It has the usual stuff thaThis is a book that one could get started on the idea of "good code" - clean, readable, elegant, simple, easy-to-test, etc. It has the usual stuff that you'd expect - good naming convention, testable code, single responsibility, short classes, short methods - but I feel like it takes them on overdose, going to extremes (IMHO) such setting short explicit lengths, forbidding certain constructs, and what seems like refactoring for the sake of it.
I'd actually recommend other books like the Pragmatic Programmer or Code Complete though; there's something about the way this book reads irks me. I think it's more useful to highlight the attributes that clean code should have (which this book does do), then it is to declare outright what is "good" and what is "bad" (even in subjective areas like readability, comments, and formatting).
To their credit, the author(s) did state right out at the start that these are their very personal preferences, so that's all right - I'm just disagreeing on some of the more subjective areas.
Also a plus are a few actual and simple scenarios/use cases to show code clean up in action, but they aren't exactly really tricky bits of code, but rather straightforward examples - very good for developers new to the concept of clean code, but less so for developers already familiar with the basic ideas....more
An encyclopedia packed full of general knowledge and facts on a wide variety of topics. A good "beginner's" encyclopedia after graduating from young aAn encyclopedia packed full of general knowledge and facts on a wide variety of topics. A good "beginner's" encyclopedia after graduating from young adult references....more
I got this book pretty late. Serves me right for not checking reviews first - sort of an impulse buy when I saw it. If you're planning of getting thisI got this book pretty late. Serves me right for not checking reviews first - sort of an impulse buy when I saw it. If you're planning of getting this book, try to find the smaller paperback instead (The World of Robert Jordan's The Wheel of Time). Why? Because the only worth it about this book is the text - unless you like big books. The artwork, as mentioned in so many reviews, is simply very amateurish, to put it politely.
The lore that you find in this book will definitely be of interest to any fan of the Wheel of Time series. But do bear in mind that the writings in this book assumes a timeline at about the first 6 or 7 books - so the stuff in the later books in the series hasn't happened yet....more
Been reading this on and off for a while now. I would put this on the "must read" shelf of anyone involved in the development side of software engineeBeen reading this on and off for a while now. I would put this on the "must read" shelf of anyone involved in the development side of software engineering, including programmers, designers, architects, even development managers. It presents a lot of important points and topics that some developers sort of know or understand but never clearly defined and put forth. There are best practices on patterns, approaches to design and development, architecture, and communication.
It takes OO development up to a new level, expanding on the generic technical ideas into the realm of domain knowledge. It's about closing the gap of understanding between business users, project owners, and and the developers.
The concepts presented take some time to absorb and are best learned when put in actual practice. It's not easy to digest but as you glean bits and pieces there, sometimes it's like, "I know doing this way always felt right", and now the book explains why it felt right. Some of the explanations are rather abstract (there are very specific examples throughout the book) for things that are hard to define, so I'd say I found it difficult to relate to things where I had no practical experience. Still, I come away from this book with a good understanding of the benefits of placing high importance on the correctness and representational value of domain model....more