Recently, I finished reading the book The Clean Coder: A Code of Conduct for Professional Programmers by Robert C. Martin (Uncle Bob) (Brazilian Portuguese version), and here are my impressions about it.

If you are inside the software development world, you've certainly heard about the legendary book The Clean Code, but there is another important book by the same author, called The Clean Coder.

The Clean Coder is not just about coding, it's about surviving in a corporate software-building environment with a high degree of professionalism and ethical standards.

The author begins the book by talking about his childhood and adolescence when he discovered his first computer, his college experience, and the unusual thing that happened to his father when he tried to get him a job.

"The Clean Coder" goes beyond the technical aspects of writing clean code and shows the reader what is on the other side of the computer screen: The professional's behaviors and attitudes.

The book covers topics such as:

• Time management and estimation
• Dealing with pressure and stress
• Communication and collaboration with team members and stakeholders
• Code reviews and feedback
• Testing and quality assurance
• Continuous learning and improvement

Martin emphasizes the importance of discipline, practice, and commitment to quality. He provides practical advice and insights from his vast experience in the software development industry, always bringing the author's lived experiences told in a humorous and easy-to-understand tone.

The book is aimed at both beginners and experienced programmers who want to improve their professional conduct and ensure they contribute positively to their teams and projects.

I liked the book, as it helped me understand some aspects that I wasn't doing correctly, and emphasized some rules that we sometimes end up forgetting.

Technical skills are something that is expected from any software programmer, but beyond that, the professional's behavior and conduct are also expected by the companies that hire them, and the book helps to deal with common situations in everyday life, such as reviewing code, and estimation, among others.

Finally, I recommend reading it for any professional who wants to improve their conduct based on valid arguments that are directed by someone who helped shape what we know today as a coder.