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

Good of you to chime in, and I think you make a reasonable argument. That said, I don’t agree with your rationale “they're always developers who want their guidelines to be explicit”: you can’t always cater to idiots, and you shouldn’t try. Making guidelines explicit is good so long as this doesn’t render them incorrect: now it’s no longer a guideline, it’s an arbitrary rule. Introducing arbitrary numbers, as you have witnessed, is a dead certain way to get shot down, and justified.

Konrad Rudolph
– Konrad Rudolph

2012-02-28 20:37:40 +00:00
Commented Feb 28, 2012 at 20:37

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 »