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

Yeah, but my experience has so far been, to follow the metaphor, that car customers don't know anything about engines, and can't tell you anything useful from looking at one. When they're in hypothetical mode, the feedback is pretty superficial "oh, that looks like it would do what we want" and you don't get much until they actually use it for the first time to solve a real problem.

Steve Bennett
– Steve Bennett

2012-05-03 09:48:43 +00:00
Commented May 3, 2012 at 9:48

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 »