[general1465]

I am calling my approach to these tasks to make them rot away. If CEO/customer wants something, I will ignore it until he will start demanding it repeatedly then I will start thinking like working on it. Because it can also happen that CEO/customer will want shiny thing you will deliver the shiny thing and he will have no clue why did you do that, because he forgot that he wanted that - the task has rot away.

[jesterson]

I wish i could have a machine to detect workforce like you and not to hire those people.

[general1465]

Consider it self-regulating system. If task can't survive in a mind of a wisher for more then few days, it was not needed from the start. Now you are saving resources and time to company which you can redirect to actually required tasks instead of some silly whims.

[jesterson]

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 you suggested.

Unfortunately this trait is not so uncommon across IT engineers.

[Lich]

> Because it can also happen that CEO/customer will want shiny thing you will deliver the shiny thing and he will have no clue why did you do that, because he forgot that he wanted that - the task has rot away.

Hate this. My boss: “Hey, why is it doing that. Who did this?” You did, you clueless idiot. You asked for it.