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.

Required fields*

Rev

How has this answer not received an upvote? It has now. Our group has found peer review to be one of the most effective tools of all, a lot more important than unit tests when it come to scientific code. It's easy to make an error when translating a complex set of equations in a scientific journal article to code. Scientists and engineers oftentimes make for extremely poor programmers; peer review can catch architectural uglinesses that make the code hard to maintain / understand / use.

David Hammen
– David Hammen

2018-07-08 14:53:32 +00:00
Commented Jul 8, 2018 at 14:53

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 »