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.
-
3This is the correct approach, not the approach taken in German public service (these two are more often than not diametral). If you do this in a public service setting, there may be fallout.Alexander– Alexander2018-02-24 12:52:21 +00:00Commented Feb 24, 2018 at 12:52
-
1Seconding that. Also remember that it is, implicitly or more likely even explicitly, op's job to keep people with technical problems from management. That is a reasonable thing to expect. It's why they pay someone else to do that job: they might simply not have the time to talk to every irritated user of technical infrastructure. So by opening up that door of people storming to management, op might already be significantly underperforming. Remember, we're talking about people that security had to remove, not people in a reasonable conflict with the it desk guy.Marcus Müller– Marcus Müller2018-02-25 12:17:21 +00:00Commented Feb 25, 2018 at 12:17
-
1"Get it in writing": op is the lowest end of the food chain, here. Not in a position to make demands on getting details of work instructions in writing. Again, op's job is to a) help people and b) keep people (thus, work) away from other people. Not to increase bureaucracy.Marcus Müller– Marcus Müller2018-02-25 12:19:34 +00:00Commented Feb 25, 2018 at 12:19
-
1Oh, and that might be a German thing: people will get angry when you start deferring blame. We have a problem, we don't care about any of your office politics, and spare us from your small talk. This is a bit different from example the U.S., or very different than for example India.Marcus Müller– Marcus Müller2018-02-25 12:26:07 +00:00Commented Feb 25, 2018 at 12:26
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**
- 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. software-industry), 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