Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with comments
Search options not deleted
user 8107
Questions about writing comments in code.
8
votes
How can I deal with a team member who dislikes making comments in code?
It doesn't matter whether the fix is comments or clearer code, but the reviewer must be able to understand it. … If something isn't clear, the best place to explain it is in the code (in comments, or by refactoring), then add the new changesets to the same review. …
4
votes
"Comments are a code smell"
I disagree with the idea that writing comments to explain the code are bad. This completely ignores the fact that code has bugs. It might be clear what the code does without comments. … The comments should explain the intent of the code, so that if there is a mistake, someone reading the comments+code has a chance of finding it. …