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.

4

I appreciate the caveat in the first paragraph. I was being intentionally provocative by saying "wrong", and certainly acknowledge that we're dealing in the realm of "best practices" and design principles, and that these sorts of things are often situational, and one must weigh multiple factors

Ray
– Ray

2012-05-09 23:23:07 +00:00
Commented May 9, 2012 at 23:23
15

Your answer reminds me of a quote that I can't remember the source of - "if your function has 17 parameters, you're probably missing one".

Joris Timmermans
– Joris Timmermans

2012-05-10 10:25:32 +00:00
Commented May 10, 2012 at 10:25
I would very much agree with this one, and apply to the question to say that yes its often a bad idea to pass in a boolean flag, but it's never as simple as bad/good ...

JohnB
– JohnB

2013-08-14 14:31:48 +00:00
Commented Aug 14, 2013 at 14:31

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 »