Comment by cratermoon
Comment by cratermoon 5 hours ago
The code is the "how", sometimes it's necessary to explain the "why".
Comment by cratermoon 5 hours ago
The code is the "how", sometimes it's necessary to explain the "why".
Sometimes I think that people who can't write well enough to convey sarcasm when they mean it should just avoid using it and say what they mean.
Sarcasm aside, yes, I 100% agree with you.
When the "why" isn't explained, you end up with things like someone refactoring code and spending time (at best) trying to figure out why some tests now fail or (at worst) breaking something in production.
I'd argue that even the "how" sometimes is better explained in plain words than in code (even if that opens the door for outdated comments when code is changed).