3 ms·
The point is not to fetishize comments. Write a comment if you feel something needs explanation, but don't freak out about "uncommented code" as a smell or wha
by ajross 4y ago
The point is not to fetishize comments. Write a comment if you feel something needs explanation, but don't freak out about "uncommented code" as a smell or whatever, when reading the code should have been your first step anyway.
And to repeat: when debugging, train yourself to ignore the comments. They will absolutely lie to you.
- baby 4y agoImo comments are like formatting. If you don’t enforce it in CI it’s going to be bad
- ajross 4y agoForcing developers to write comments[1] just to get code merged seems like the best possible way to ensure those comments are lies. [1] Which, it's important to point out since you used the term "CI", are fundamentally untestable. There's absolutely no way to ensure a comment is correct. A CI smoke test at the very least verifies code builds and doesn't break pre-existing cases. No such validation is even theoretically possible for comments.
- baby 4y agoI’ve seen it done before and no, it was beautiful, everything was commented