|
At least the company recognizes this a juvenile way to deal with conflict. You are wrong I am right set aside, this behavior hurts already incompetent companies. In the real world not everyone agrees and that is okay. So kudos to that director.
|
|
|
|
|
I am Questioner, Question all expectations (And I know they are non-sense  ) so I then acts like Upholder, dig my own exceptions and fix them 
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
That's actually exactly what a Questioner is meant to be like: they essentially convery external expectations into internal expectations and then uphold them (now that they actually make sense).
I think most devs do this: translate from external gibberish to internally well-formed commands.
cheers
Chris Maunder
|
|
|
|
|
Mostly I meet expectations, but I question them if they are silly, I refuse some if they are stupid, and I'll meet silly and stupid ones if there are damn good reasons for it.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I refuse to question silly ones only to let the work show how stupid the request and requester is thinking they had a damn good reason for an expectation from me that never would exist of my own doing.
Problem is, this doesn't always work as planned. (a thousand  's)
|
|
|
|
|
A real fact though! Nice One!
|
|
|
|
|
I would have to say rebel-upholder
<sig notetoself="think of a better signature">
<first>Jim</first> <last>Meadors</last>
</sig>
|
|
|
|
|
Yep, all those options should have been with check-boxes.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
