3 ms·
I remember sitting in a meeting some years ago and we were discussing a new issue tracking system that was being demoed on the projector. The editor component
by ilaksh 14y ago
I remember sitting in a meeting some years ago and we were discussing a new issue tracking system that was being demoed on the projector. The editor component took a full 10 to 15 seconds to load into the page every time. So I said "that editor sucks". It was one of the few things I had said during the meeting.
The manager was very irritated and said something like "We don't tolerate that kind of negativity here". And continued, as if I had said something awful. He said something like "unless you have a solution to a problem" something something in the process of explaining why I shouldn't say that.
So five minutes after the meeting I found out how to disable the slow graphical editor and then the issue tracker became usable for normal people.
Well, I guess I am a negative person then. If it sucks, it sucks.
I will try to take some of this advice constructively though, because I do spend a lot of time focusing on problems that need to be solved. But I can't help but think that the reason a lot of people aren't so critical or 'negative' is that they have just given up on fixing things, or are just so generally ineffective at problem solving that they naturally accept everything as it is.
I would rather be a negative bastard who identifies and solves problems than a happy ineffectual drone who just goes along to get along and accepts the status quo no matter how broken.
- SoftwareMaven 14y agoIf you solve problems, negativity isn't as much of a problem. If you spend all your time finding problems that other people should be solving, that is more problematic. I think we tend to be negative, especially wrt software, because we know how it could be. So we apply that filter without also applying the "what did it take to get where it is" filter.
- lutterkd 14y agoThe problem isn't that you raise the issue, the problem is the aggressive language "sucks". Not has problems, not is limited, "sucks". The guy writing it probably knows it has problems. He's probably working really hard on it. Maybe he stayed late at work to try to improve it, instead of seeing his girlfriend. And you come along and just say "sucks". Even if he wasn't there, you're still having a go at him in front of other people. Being polite, diplomatic, calm and considered is not being an "ineffectual drone". You're falling into that mindset that you have to be a cunt to get stuff done. You don't.
- aninhumer 14y agoThis is exactly the kind of thing the article is complaining about. You could say "that long load time is going to be bad for productivity", it's a valid criticism and deserves a response by whoever is explaining the tool. But you don't, you say "that editor sucks". It's aggressively negative language which doesn't even specify a problem. Whoever is recommending this system is likely nervous, and very invested in what people think of it, so you saying "it sucks" will feel like a personal attack. It's completely unnecessary.