User rant

[Cogman]

We have an internal tool. It has a feature that often breaks, has an alternative, adds an ugly mess of dependencies to our project, and does something totally retarded to boot.

This user, and it is only one, has fought at every turn our removal of this feature. Every other user has adopted doing things differently except for them. So I decided, enough is enough. I reach out to my manager, my managers manager, several people who have been involved in the process of removing this thing and got approval to remove the feature.

Now, here is the fun part. I get to sit through and listen to this user *redacted*, moan, complain, and throw up the biggest stink ever (which really is the only reason nobody else has removed this feature).

Gee this is going to be a fun week.

And now I have to "make a small stink" about swearing in the tech forums. Which you shouldn't do. -- Programming Moderator Ken g6

 

[Crusty]

There's some other reason said user is extremely against fixing the issue.

My gut feeling is that said user uses the breaking of the tool as an excuse to not work or to under-perform at their job, and having something that actually works well means they have to do their job AND be accountable for it.

 

[dave_the_nerd]

There's always one.

 

[Cogman]

Well, we pushed off the removal of the feature until July. This user admitted that they really just didn't want to change (and not that the feature was actually necessary). We pushed off the removal because we have quarterly reporting obligations and we didn't want to rock the boat too much right before a quarter.

However, come july, that code is gone for good.

 

[slugg]

There's some other reason said user is extremely against fixing the issue.

My gut feeling is that said user uses the breaking of the tool as an excuse to not work or to under-perform at their job, and having something that actually works well means they have to do their job AND be accountable for it.

This was my first thought, too.