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

1

Biggest bang-for-buck is more like a few ASSERTs in the right places.

Peter Mortensen
– Peter Mortensen

2015-05-20 22:39:21 +00:00
Commented May 20, 2015 at 22:39
@PeterMortensen True, but only if you know what the right places are.

Emilio M Bumachar
– Emilio M Bumachar

2015-05-21 16:28:47 +00:00
Commented May 21, 2015 at 16:28
You beat me to it. No matter in which direction the OP takes his team, getting there with Git will be much easier and more productive than without.

dotancohen
– dotancohen

2015-05-22 23:44:38 +00:00
Commented May 22, 2015 at 23:44

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 »