Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3

I am not sure this is the best idea. Much better to let people find their own mistakes rather than publicly asking a group why their code isn't good.

sixtyfootersdude
– sixtyfootersdude

2012-01-25 21:08:18 +00:00
Commented Jan 25, 2012 at 21:08
1

@sixtyfootersdude I think code reviews are more effective when done as a group since it promotes wider spreading of knowledge across the team.

Dan Is Fiddling By Firelight
– Dan Is Fiddling By Firelight

2012-01-25 21:32:13 +00:00
Commented Jan 25, 2012 at 21:32

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »