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

I know where you are coming from, but I don't believe that your last statement is a fair representation of the situation. Yes, both interfaces deal with the view, but the concepts they represent are totally orthogonal. So I would restate it as A class, or base class, implementing multiple un-related blocks of code is a bad design, because putting all the code in the one base class intertwines it and you now rely on the good graces of the coder not to screw up and change one interface implementation when he meant to change the other.

Peter M
– Peter M

2017-11-09 14:37:52 +00:00
Commented Nov 9, 2017 at 14:37

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 »