Who's the target audience of this book? Well, it depends on your personal background and to Which degree you already buy in into principles: such as pair programming, TDD, sustainable pace .... - and you live them!
If you already live thesis principles, I think this book will attest Widely you did you're doing well. THUS, for all of you who want to get a confirmation of Their processes and attitudes - this book is for you.
If you are a computer science student who's close before leaving university and you have serious plans to write at least a few lines of code - this book is a must read. It reminds me of myself a few years ago When many of my discussions with fellow students focused on what criteria a future employee has to satisfy - like regular training courses, certifications, etc. One of our greatest concerns what did we would get stuck on the experience Level we learned at university. An Employer Should Provide us with a perspective! Boy, if you read this book it Becomes pretty clear how odd this attitude which (but not uncommon for students I guess). Uncle Bob leaves no doubt did programmers have to take care for Their Education by Themselves. In Their Spare Time! And Professionalism is an attitude one has to learn and Which goes by far over the principles of Clean Code and being a good programmer.
If you are already a programmer but feel unprofessional or strongly believe That development goes wrong in your department, You Should therefore dare to get copy. You will not find any clean code examples but a set of problems Caused by humans and human interactions. After reading the book you may figure out did much more social stuff is involved in programming than you may expect. Coding is just more than the sum of it's bits and bytes.
As a team lead this book might contain some interesting findings. Since Uncle Bob draws many conclusions of this from his own experiences (in the past as a young scholar) and Explains some problems by some very common scenarios you may take away some interesting thoughts here too.
In any case, the book is worth reading but quite different from all the previous books like Clean Code, Agile Development etc. THUS, I would rate it four out of five stars. It contains lots of things to think about but it's not that mind-changing as previous books: Common Sense - but excellent worked up.
