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

Though you'd probably consider me one, I lol'd on the 'rheumatic brains'...

Marjan Venema
– Marjan Venema

2013-01-15 10:13:35 +00:00
Commented Jan 15, 2013 at 10:13
1

I don’t think the term “user story” can be applied here. User stories describe business requirements for a software.

Konrad Rudolph
– Konrad Rudolph

2013-01-15 11:37:57 +00:00
Commented Jan 15, 2013 at 11:37
Yeah, I think he means "use case".

Jörg W Mittag
– Jörg W Mittag

2013-01-15 13:19:21 +00:00
Commented Jan 15, 2013 at 13:19
Downvoted: no word about a strategy how deal with the mentioned cases.

try-catch-finally
– try-catch-finally

2016-06-17 12:32:31 +00:00
Commented Jun 17, 2016 at 12:32

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 »