02.09.2024 **Tags** #areas/dev #areas/reading # My Alignment towards the Heuristics of Clean Code I think a pragmatic way to rate this book and its heuristics is by deciding how aligned - meaning how much I agree with the heuristic - from a score from 1 to 5 I am. The rating is defined as follows | Rating | Meaning | | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 5 | **Strong Agreement**<br>I try to actively follow the heuristic during my everyday programming work | | 4 | **Agreement** <br>I personally agree with the heuristic, but I don’t try to actively apply it all the time during my everyday programming work | | 3 | **No Agreement or Disagreement**<br>Scores 3 and lower have their own individual explanation | | 2 | **Disagreement**<br>I personally disagree with the heuristic, but I probably won’t try to immediately fix code written according to the heuristic during my everyday programming work | | 1 | **Strong Disagreement** <br>I try to actively “fix” code which is written according to this heuristic during my everyday programming work | The following heuristics that I mention have no claim in terms of completeness. I started with extrapolating the heuristics from the prose of the individual chapters, and I already have noticed ones that are not of the book’s chapter 17, which is a collection of (smells and) heuristics. I will also ignore heuristics that are very Java-specific, as I am not a Java developer and only interested in universally applicable heuristics. # References [[Clean Code - A Handbook of Agile Software Craftmanship - Robert C. Martin.pdf]]