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.

2

I'm afraid I don't understand what you meant...

deprecated
– deprecated

2011-09-12 20:28:54 +00:00
Commented Sep 12, 2011 at 20:28
2

@vemv: I think he means by "proper level of abstraction" that you don't end up with code that has different levels of abstraction mixed (i.e. what Kilian Foth already said). You don't want your code to handle seemingly insignificant details (e.g. the formation of all bonds in fuel) when the surrounding code is considering a more high-level view of the situation at hand (e.g. running an engine). The former clutters the latter and makes your code less easy to read and maintain as you will have to consider all levels of abstraction at once at any time.

Egon
– Egon

2011-09-12 22:02:52 +00:00
Commented Sep 12, 2011 at 22:02

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 »