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

Down vote if you will. It still doesn't change the fact that pattern-driven development is silly. Patterns exist to facilitate talking about code. They aren't recipes, blueprints, or out of the box generic solutions. Treating them as such limits you tremendously. Instead, be pragmatic when coding. Solve your problem the way that best suits your program.

MetaFight
– MetaFight

2016-07-09 12:11:11 +00:00
Commented Jul 9, 2016 at 12:11
2

Exactly. OP is approaching this backwards. If you don't know what pattern to use, then forget about the patterns, make something that works, then see if what you did could be described by one of the existing patterns. Notice: not everything will be neatly described by the GoF design patterns.

whatsisname
– whatsisname

2016-07-09 16:19:34 +00:00
Commented Jul 9, 2016 at 16:19

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 »