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! for "..you should be telling objects what to do ..". And "..thinking too low level.." Finally, kudos for the "minimize dots" heuristic. Nicely explained.

radarbob
– radarbob

2012-04-06 20:30:49 +00:00
Commented Apr 6, 2012 at 20:30
+1 for suggesting he think outside the low level box he's in and for the "why" and "what" to guide the process.

Patrick Hughes
– Patrick Hughes

2012-04-06 22:13:02 +00:00
Commented Apr 6, 2012 at 22:13
+1 for the higher level idea. Probably it would be the best to have a low level wrapper for the communication stuff PLUS an interface that defines high-level logic. These are two abstraction levels that deserve to be treated separately.

Olivier Jacot-Descombes
– Olivier Jacot-Descombes

2012-04-07 21:22:08 +00:00
Commented Apr 7, 2012 at 21:22

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 »