Scan barcode
mcormier's review
4.0
There is a lot of good stuff in here. My main gripe is that the author refers to blog posts in the book and simply states, this guy explains the x pattern well. Well that's great but I bought a paperback book with the intention of using it as a complete reference in the future. As time goes by these blog posts may disappear so this would be a more complete tome if the author did the extra work and summarized the information of these blog posts in his own book.
The paperback copy is quite affordable at $20 but unfortunately it is printed by amazon. This is the second technical book I've read that was published by amazon and like the previous it shows. The extra sheen, type setting, and font choices that a publisher would add to polish a book are missing. Welcome to the future where everyone can self publish but it looks half-ass.
I plan to use this book as a reference and apply some of the techniques described as time goes on so it is premature for me to give a proper review.
One thing that stuck out like a sore thumb for me was the following near the end of the book.
"I prefer to eliminate locals whenever possible. This preference is based on the conceptual overhead introduced by locals".
This is near the end of the book and Jay spends time eliminating locals. There is no proof that he provides that locals introduce conceptual overhead. Good grief, if you are a koder and can't deal with locals then you need a new profession. Just sayin'.
The paperback copy is quite affordable at $20 but unfortunately it is printed by amazon. This is the second technical book I've read that was published by amazon and like the previous it shows. The extra sheen, type setting, and font choices that a publisher would add to polish a book are missing. Welcome to the future where everyone can self publish but it looks half-ass.
I plan to use this book as a reference and apply some of the techniques described as time goes on so it is premature for me to give a proper review.
One thing that stuck out like a sore thumb for me was the following near the end of the book.
"I prefer to eliminate locals whenever possible. This preference is based on the conceptual overhead introduced by locals".
This is near the end of the book and Jay spends time eliminating locals. There is no proof that he provides that locals introduce conceptual overhead. Good grief, if you are a koder and can't deal with locals then you need a new profession. Just sayin'.
jakemcc's review against another edition
5.0
This is a book I plan on strongly recommending to other developers. Jay Fields presents his strategy for testing and his definition of a unit test. The book starts with some marginal unit tests and slowly improves them. I found myself feeling uncomfortable with the initial version of the tests and it was rewarding seeing the tests improve and having that uncomfortable feeling disappear.
Why do you write tests? What do you try to get out of testing? How do you make failing tests useful? By the time you finish this book you should have a been driven to think about those questions and more. Even it you don't agree with Jay's approach this book will make you think.
You should read this book.
Why do you write tests? What do you try to get out of testing? How do you make failing tests useful? By the time you finish this book you should have a been driven to think about those questions and more. Even it you don't agree with Jay's approach this book will make you think.
You should read this book.