Jason Antic

Same here. Comments are often either misleading/outdated or extremely redundant (“//now I’m adding two things together!”). And the compiler doesn’t care. Also less emphasis on comments I think drives more emphasis on clear code. “Code should read like a book”.https://twitter.com/Chrikomu/status/1191778623784734721 …

That all being said, of course there’s exceptions. If your code is doing something exceptionally weird or unexpected- yes- please explain.

I respectfully disagree. Commented code is a basis for all stuff in documentation. Imagine large and shuffled teams with new additions working on an ever growing project. How would a newbie comprehend? Even skilled devs would save a lot of time with comments in place.

Good code can go way further than any comments to convey actual reliable understanding of what’s going on. But if you’re not dealing with good code then yeah- you’ll need the comment crutches!

True. In my limited experience, I think that at a certain point, despite all the reviews, clean-up and sprints dedicated for code efficiency, every code rots. Devs won't remove some code cuz it will break a feature. Sometimes refactoring's nightmare. Commenting is practical.