You cannot tell at a glance whether code is “clean” or not, yet most developers seem to attribute more value to code that’s pleasing to look at rather than code that is consistent, readable and understandable. We’ll discuss some of the shortcomings with some commonly accepted indicators of “clean” code, as well as some principles to follow for truly cleaner (and maintainable!) codebases, regardless of language.

Learn that comments are not a crime, a_rose() by any other name might not smell as sweet, and HungarianNotationStr might not be as outdated as you might think (though we can pretty it up a bit). We’re not re-etching the laws in stone, but we’ll discover some pretty good best practices.


Comments are closed.