I guess the entire point of the book is to just try to make your code readable for others, not just to yourself.
About Casey's writing I'd say that he is probably one of the best developers alive, I've never came across a code that would clean up over time.
I like to practice a few of its principles because I know how hard is to read someone else's code and be completely lost for hours on simple things.
I believe that single purpose functions, few parameters, size and scope of classes and functions matter and most importantly: comments lie. A bug fix will not fix a comment.
It is impossible to write perfectly clean code, but is very good to have a few sets of rules to help you manage an always growing application.
Surely it is not as important when you are a single developer or working on a very small team (2-3 people), but becomes increasingly important as your team grows.
I guess the entire point of the book is to just try to make your code readable for others, not just to yourself.
About Casey's writing I'd say that he is probably one of the best developers alive, I've never came across a code that would clean up over time.
I like to practice a few of its principles because I know how hard is to read someone else's code and be completely lost for hours on simple things.
I believe that single purpose functions, few parameters, size and scope of classes and functions matter and most importantly: comments lie. A bug fix will not fix a comment.
It is impossible to write perfectly clean code, but is very good to have a few sets of rules to help you manage an always growing application.
Surely it is not as important when you are a single developer or working on a very small team (2-3 people), but becomes increasingly important as your team grows.
this is so true