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.

"the code is badly written" would then connect back to something tangible, like performance, readability, security or bugginess. As for "its really hard to understand the code" I agree it is a harder route but code that is hard to read is hard to understand and will lead to bugs, and they cost money. So there is definately arguments for just making the code look pretty, consistent and reader friendly as well.

Jonas Schubert Erlandsson
– Jonas Schubert Erlandsson

2016-11-21 13:22:32 +00:00
Commented Nov 21, 2016 at 13:22

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 »