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.

This general rule has been given a name: YAGNI.

candied_orange
– candied_orange

2022-03-30 12:58:50 +00:00
Commented Mar 30, 2022 at 12:58
Right, but I guess for this to apply you either need to be sure that a more complex solution is never going to be needed, or there is a possible migration from the simple to the more complex solution if it ever becomes necessary.

Jan Gassen
– Jan Gassen

2022-03-30 14:08:08 +00:00
Commented Mar 30, 2022 at 14:08
I'm not saying you should use a bad or non-expressive design. I'm just saying don't introduce abstractions that don't help you now. Use the best and simplest design for your current case. Don't, in general, do things just out of habit, or a sense of "cleanliness", or because of something you think you will need later. Easier said that done, sure, but such is software design.

Robert Bräutigam
– Robert Bräutigam

2022-03-30 19:35:52 +00:00
Commented Mar 30, 2022 at 19:35

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 »