4 ms·

It's not a "regulating system" of any kind, but plain passive aggressive arrogance. I know better what to do so I would just pretend like I am going to do what

• general1465 7mo ago
  > It's not a "regulating system" of any kind, but plain passive aggressive arrogance. Is it arrogance if the task won't stick? Because if it won't stick, it was not needed at the first place - system just regulated itself to have less workload. > I know better what to do so I would just pretend like I am going to do what you suggested. I would argue that developers probably know better what to do. Look on it from developer's perspective he has tasks which are supposed to be done yesterday, he is being pushed by his PM and then CEO comes in with completely wild and random task which will push existing tasks further down the line. And this is going to be done without any regard to existing tasks, existing deadlines and without any regard to ticketing system. So the best course of action, is to take no action and see if this random task will stick. In most cases it won't stick, because task is more a random thought than something to be worked on.
  • jesterson 7mo ago
    > Is it arrogance if the task won't stick? Yes. Because stick/not stick is "decided" by IT Engineer by excerpting leverage over someone who actually have decision making capability - a manager. And what it is "stick/non stick" in your perspective is just manager thinking how to make things work bypassing the annoying engineer. > I would argue that developers probably know better what to do Aaaand that's exactly where arrogance is. If developers "know better" why don't they become product owners/visioners?