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.

1

Similarly, take time to watch the people using your product - see how they actually do things; make notes as they do, then discuss with them after to prioritise improvements.

Peter Boughton
– Peter Boughton

2010-09-09 18:02:18 +00:00
Commented Sep 9, 2010 at 18:02
1

Oh, and make sure they know you're doing it to make the software better; you're not judging them!

Peter Boughton
– Peter Boughton

2010-09-09 18:02:49 +00:00
Commented Sep 9, 2010 at 18:02
The intent was to have a fun question, but it's nice to see some useful answers.

Tamara Wijsman
– Tamara Wijsman

2010-09-09 18:04:27 +00:00
Commented Sep 9, 2010 at 18:04
2

I way too often think a person is an idiot but force myself to listen, only to realise they are talking sense. Then again, there are times wasted on fools.

Dan
– Dan

2010-09-10 15:28:26 +00:00
Commented Sep 10, 2010 at 15:28

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 »