Status Updates From The Clean Coder: A Code of ...

Exploratory Testing 5%
Integration Testing 10%
System Testing 10%
Component Testing 20%
Unit Testing 50%

Testing, testing, testing and communication.

Practice, practice, practice.

The three rules of TDD will I remember them? Don't write any production code until you have a failing test. Don't write any more test code than is sufficient to fail and not compiling is failing. Don't write more production code that is sufficient to pass the currently failing unit test.
I had to look it up, the second and last sentences. They are not fluent enough and as negatively defined hard to understand.

I just read that part on mentoring younger developers where he said that books don't help making good or better programmers of them. I assume this also counts for his books. So it makes sense for me to read his books as I'm older and more experienced. But how old should you be, or how experienced?

Reading “Saying No” resonates hard with a similar situation I’m having, glad I’m not alone

Very engaging, the authors tone is very straightforward but I disagree with some of his ideals on the employee / employer relationship

Restarting reading and joy! Each chapter is a jewel of being a professional software developer. A must from beginners to seniors!

افراد بسیار اندکی هستند که زمانی که چیزی می‌گویند، قصد آن را دارند و سپس آن را واقعا انجام می‌دهند. برخی دیگر نیز هستند که چیزهایی می‌گویند و قصد آن را دارند اما هرکز آن را آنجام نمی‌دهند؛ و افراد بسیار بیشتری وجود دارند که وعده می‌دهند و حتا قصدی برای انجام آن ندارند.

‏حرفه‌ای‌ها حقیقت را به صاحبان قدرت می‌گویند. حرفه‌ای‌ها، شجاعت نه گفتن به مدیران خود را دارند.
...
بردگان اجازه ندارند نه بگویند. اما از حرفه‌ای‌ها انتظار می‌رود نه بگویند. در واقع مدیران خوب، طالب کسی هستند که جرات ‎نه گفتن را داشته باشد.

To be honest, this is the first book I have ever read from Uncle Bob. While some of the statements described here (the chapters dedicated to estimate and work ethic are worth to read) are very useful and atemporal, other writtings didn't age well or at least they were not so interesting for me, like the tooling chapter or the examples based in the 70' - 80' experiences he lived. Even that, a very good reading.

Just wanted to read the first three chapters and save time later for the next chapters. I just finished for the time being.

At Chapter 11

Through Chapter 5

Just read Time Management chapter. Really liked the part where he talks about swamps and avoiding them. I sometimes feel like that and I definitely need to be better at spotting this kind of problem. Also, I think I got convinced of trying Pomodoro.

Capítulos del VIII al XII

Capítulo VII

Capítulos III, IV, V, VI

Capítulo II. Aunque versa sobre el no en un entorno laboral, se puede aplicar perfectamente a las relaciones personales

Prólogo, introducción y capítulo I.

Very helpful advice so far!

While most of thing that was written is obvious for a software engineer like me. It still serves a everyday reminder of what I need to do to become a professional software engineer.

Uncle Bob (Robert C Martin) is like a strict but well-meaning uncle. It might be too harsh to apply this advices to reality with its utmost accuracy but they are quite practical and useful.

So far, I am liking it. I have just finished the first chapter and it is interesting. I do lots of reading but nevertheless, it made me feel that I am still not copping with changes in the industry as a programmer.

I really enjoyed reading this book it really illustrate some of the developer daily conflicts and it gives some practical advice on how to smoothly solve them and have a mutual consent with different software project stakeholders, and also enjoyed the mentioned examples from Uncle Bob's past experiences.

Barely worth 3 stars.
That's subjective, and includes the amount of information that I personally got out of this, and the author's style of writing. His style I find to be extremely un-nuanced, and preachy.

With all due respect for his career and stuff he accomplished, I feel like this book is just him talking unrestricted for a short time, telling us things he hates, loves, and spreading propaganda.

Chapter 2: Saying No
Chapter 3: Saying Yes

Chapter 1: Professionalism

Like the book "User Story Mapping", it feels like the anecdotes and bad examples were written at the beginning in the book. This might be a marketing strategy, so that if the best material is at the end, it will influence the review score. Good strategy, but I caught on to it, so I'm not forgiving the author.
Lots of good and common sense advice. Still very opinionated and non-nuanced, but getting slightly better

30% done
Very biased, opinionated and un-nuanced book. The author is just providing anectodes and using them to encourage a certain type of attitude
While the attitude of "write quality code, and learn every day" is fine, it feels like the author doesn't acknowledge or understand how business is performed. He's too tied up in the code, and doesn't understand the business side. This is not agility, it's dogma