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.

While these guidelines may or may not be helpful, it doesn't really have anything to do with the SRP as defined in SOLID, does it?

sara
– sara

2016-07-03 07:14:30 +00:00
Commented Jul 3, 2016 at 7:14
2

THANK you. I can't believe some of the insanity involved in so-called SOLID principles, where they make very simple code a hundred times more complex for no good reason. The points you give describe real world reasons to implement SRP. I think principles you gave above should become their own acronym, and throw "SOLID" out, it does more harm than good. "Architecture Astronauts" indeed, as you pointed out in the thread that lead me here.

Nicholas Petersen
– Nicholas Petersen

2018-01-17 19:02:13 +00:00
Commented Jan 17, 2018 at 19: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 »