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

"puts you in a better position to offer a solution, not a problem." - yep, which is the main point of this post. I didn't expect it to blow up quite like that.

MK_Dev
– MK_Dev

2012-07-03 04:35:36 +00:00
Commented Jul 3, 2012 at 4:35
In the end, it will either be a team success, or a team failure - and no matter what the course of action may be (including the blame game) will not work, or even be proven a bad idea, if not followed through to fruition or failure. In other words, the alternative to mutiny, may in fact be to just follow your bosses plan to the letter, with active participation by all - towards the inevitable collection of hard data, to weigh in favor of, or against, continuing down that path of reason.

tahwos
– tahwos

2012-08-13 01:17:11 +00:00
Commented Aug 13, 2012 at 1:17

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 »