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.
- That is completely hopeless advice, i foresee a "shop" with really bad work environment for you. Urgghh!cognacc– cognacc2016-07-03 14:48:12 +00:00Commented Jul 3, 2016 at 14:48
- @cognacc - You needn't 'forsee' anything. I have been working in groups for 25 years where we have a very good work environment: We're all adults and understand what it requires to be professional and to have accountability for our work.Vector– Vector2016-07-12 14:21:44 +00:00Commented Jul 12, 2016 at 14:21
- 1I have to agree with Vector. If it's part of the process, everyone does it and I'm sure they quickly see that "it doesn't bite". There's always a risk of some people being "rude" in their comments in a code review, of course, but then it's those people that need to be dealt with - just like they would be if they were rude to their coworkers in person.MetalMikester– MetalMikester2016-10-19 12:01:26 +00:00Commented Oct 19, 2016 at 12:01
- I agree with cognacc, it is useless advise because it does not suggest a strategy or solution. It just says "they must because they have to". Duh. The question is how to deal with them, as in how to turn them around. Just making people do something against their will (or else) is not fixing the problem, it is likely creating new ones. You must first understand the origin of the resistance.Martin Maat– Martin Maat2016-10-19 12:45:25 +00:00Commented Oct 19, 2016 at 12:45
- You missed my remark well managed shop and all that follows therefrom: That means you're dealing the adults: People who know what their job means and entails. You failed to comprehend my abundantly clear answer.Vector– Vector2016-10-20 16:22:54 +00:00Commented Oct 20, 2016 at 16:22
Add a comment |
How to Edit
- 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
How to Format
- 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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you