The book looks great actually, and I agree with the first sentiment about S.H.I.T, but the author incorrectly assumes that tests are used as a reliability indicator. Maybe some do use it for that, but most teams don't. Tests are regression detectors. Tests are there to prevent you from causing unintended behavior change while changing other parts of code. Tests never tell you if your code or even if your spec is reliable. They just tell you that code adheres to the given spec.
I also dislike TDD but for a different reason: it incorrectly assumes that spec comes before code. Writing code is a design act too. I talk about that in Street Coder.
Started with BOOBS as I spent a lot of time in EnterpiseFizzBuzz and laughed a lot. I will certainly come back to the rest of the chapters but wanted to acknowledge your great writing.
I would start reading from the glossary on pages 63-64, which pretty much summarized the main points of the book. The remaining pages felt mostly like flavor text.
9 comments
[ 2.0 ms ] story [ 33.7 ms ] threadI also dislike TDD but for a different reason: it incorrectly assumes that spec comes before code. Writing code is a design act too. I talk about that in Street Coder.
The author looks legit - or at least has contributions for over a year.
But github is free & idk if they scan user repos for malware
Are .pdfs and .epub safe these days?
Always good advice.