Respectfully, I think this article contains some really terrible advice. Based on his examples, I think his chief complaint should really be that programmers sh

Respectfully, I think this article contains some really terrible advice. Based on his examples, I think his chief complaint should really be that programmers should stop writing unnecessary comments, which I’m actually okay with. If you can’t write expressive code, own up to your failure and write a comment. You are responsible for the code you write, so never leave poorly written code unexplained. While in theory it’s possible that every member of your team could write code that’s so expressive that it never need comment, in reality you’ll find that different programmers adhere to different naming/styling conventions and sometimes being able to see the author’s steps laid out in comments leads easier corrections to errors in logic or better refining of the process itself. Good code commenting practice means that new team members can more quickly adapt to the codebase, or even programmers who are coming back to their older work after some time or a major life event. Invariably there will be times where programmers naturally go through cycles of sprint/crunch and code cleanup, it’s the nature of the work.