re: Identifying the dirt in our code - names, functions, and comments VIEW POST


Cursory response that avoiding comments isn't the answer; rather, ensure they only state why the code is there, not what it does. (If code and intent-comment ever mismatch, that often indicates a bug that should be addressed.)


You made a very good point
Great article, by the way (:

code of conduct - report abuse