A must read for software engineers. There are probably a ton of better reviews than I can ever write. The initial 100~ pages are must reads. And the fA must read for software engineers. There are probably a ton of better reviews than I can ever write. The initial 100~ pages are must reads. And the further you get in the book the more okay (in my opinion) it is to skip a chapter. It could probably have been two books, as the latter parts are more specific patterns and practices. I am glad i read it and even though I skipped parts of the end, I imagine I'll reread those either when specifics might be of interest (as a compendium) or when i just feel it's worth to reread, which i assume i will someday....more
First part is a must read for any developer and us still very relevant today. The latter parts are less critical to read, but still does contain elemeFirst part is a must read for any developer and us still very relevant today. The latter parts are less critical to read, but still does contain elements worth reading, especially from a TDD perspective. You don't have to agree with the book, but understanding it's perspective is quite valuable. It's also a quick and fun read. Took me a few weeks....more
Loading...
