The Clean Coder, Chapter 3 & 4

Chapter 3 and 4 of The Clean Coder by Robert C. Martin explains when to say “yes” in workplace and what are some of the authors personal definitions and experiences of good or bad coding practices. Author also explains some strategies on what is good coding practices and how to become a successful, efficient and professional coder.

For me personally, these two chapters were as interesting and informative as the first two chapters of this book. I really liked how the author talked about the importance of time and being late. Author said, “regularly measure your progress against your goal, and come up with three fact-based end: best case, nominal case, and worst case.” The reason why this phrase resonated with me is because I was discussing with my group and Dr. Wurst earlier that how I feel like the daily scrums are happening too often for me during the week. I am too busy during the week and I barely get anything done. So, for the daily scrums I won’t have anything significant to talk about or offer to the group during week that can show that I am progressing and not stagnant in my contribution to the team. Dr. Wurst respond was that I do not have to say what I cannot deliver. He elaborated that some team members might have time during week days and can get done more during that period. While some group members might be busy during week days and can contribute more over weekend. In either case, commit to a time and task; and deliver it. This gives team members a clear picture of where the member is and what he/she is doing. This is what the author also suggests that be transparent with your team members. If you are going to be late on a task that you committed to. Let your team know about it that you committed to this task, but this is how much progress you have made so far and this is your plan to finish it up. If you are stuck, ask for help from your team members. There might be a member who might have a solution to your problem or you can do pair programming with another team member. The bottom-line is that be honest and transparent with your team.

It was a joyful and learning read for me. I look forward to more reading and writing about this book!!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s