3 ms·

A big YMMV on what I'm about to say, but: in my experience, the biggest complainers at work are the most responsive and productive people. Because when a new re

A big YMMV on what I'm about to say, but: in my experience, the biggest complainers at work are the most responsive and productive people. Because when a new request comes through, they're the ones who have already jumped in. They're mentally working through what it will take to get this done, wrestling with the difficulties and verbalizing them. Others are nodding and smiling but not really engaging with the problem yet.

ilrwbwrkhv 4y ago
I think there is something to it. The ones who complain but still trudge through are amazing. They highlight pain points and solve them at the same time.
- ExtremisAndy 4y ago
  That's the key: they still trudge through it. I fully agree that those people are indeed amazing. In my experience, though, many complainers toss out every objection possible hoping to make the new project seem so difficult that it isn't worth doing (so everyone will just drop it). Those complainers are toxic and can kill progress. But yes, the ones who verbalize issues just to make sure everyone has a full understanding of a project and the challenges in completing it... but still have every intention to conquer those challenges and stick with it to the end... yes, give me those types of 'complainers' ANY day :)
  - ChrisMarshallNY 4y ago
    As an "old warhorse," I can tell you that I have been labeled a "complainer," because of such "complaints" as "Have you considered what happens when the user does X?" or "I tried pretty much the same thing, last year. It didn't turn out the way I wanted. Here's what happened..." or "Is that thread-safe?" or "Are you sure that will never be called on another thread? You do have a few network closures, here." or "Did you make sure that you let the connection go, after sending that instruction? It will result in power drain, if not." etc. Real killjoy.
  - javier2 4y ago
    From my point of view, we get a new project that I think will take 6 weeks because of X, Y Z. Management thinks it should take 2 days, so they say go ahead anyway. The project takes 8 weeks to finish most of the features and doing this effort forced us to drop every other thing we were already maintaining and working on. Everything is late, the targets set for the year miss as we spent 2 months on this other project and nobody is happy.
  - JohnFen 4y ago
    Those types of complainers are certainly better than the types who don't actually do the tasks. But even better are those who do the tasks without burdening their coworkers with complaints.
- deleted 4y ago
  [deleted]
LeftHandPath 4y ago
I’ve found that complaining is productive but has a social cost. But I and others absolutely do work this way. I started opening GitHub issues I never expect anyone else to read to help myself explore and verbalize a problem without having to nag anyone else about it; it’s been helpful and also yields a lot of what is effectively documentation of the “why” behind our design choices. Not sure if it would work as well on public repos or if you work with anyone that tries to max their GitHub stats (eg average issue close time) though.

ilrwbwrkhv 4y ago

I think there is something to it. The ones who complain but still trudge through are amazing. They highlight pain points and solve them at the same time.

ExtremisAndy 4y ago
That's the key: they still trudge through it. I fully agree that those people are indeed amazing. In my experience, though, many complainers toss out every objection possible hoping to make the new project seem so difficult that it isn't worth doing (so everyone will just drop it). Those complainers are toxic and can kill progress. But yes, the ones who verbalize issues just to make sure everyone has a full understanding of a project and the challenges in completing it... but still have every intention to conquer those challenges and stick with it to the end... yes, give me those types of 'complainers' ANY day :)
- ChrisMarshallNY 4y ago
  As an "old warhorse," I can tell you that I have been labeled a "complainer," because of such "complaints" as "Have you considered what happens when the user does X?" or "I tried pretty much the same thing, last year. It didn't turn out the way I wanted. Here's what happened..." or "Is that thread-safe?" or "Are you sure that will never be called on another thread? You do have a few network closures, here." or "Did you make sure that you let the connection go, after sending that instruction? It will result in power drain, if not." etc. Real killjoy.
- javier2 4y ago
  From my point of view, we get a new project that I think will take 6 weeks because of X, Y Z. Management thinks it should take 2 days, so they say go ahead anyway. The project takes 8 weeks to finish most of the features and doing this effort forced us to drop every other thing we were already maintaining and working on. Everything is late, the targets set for the year miss as we spent 2 months on this other project and nobody is happy.
- JohnFen 4y ago
  Those types of complainers are certainly better than the types who don't actually do the tasks. But even better are those who do the tasks without burdening their coworkers with complaints.
deleted 4y ago
[deleted]

LeftHandPath 4y ago

I’ve found that complaining is productive but has a social cost. But I and others absolutely do work this way. I started opening GitHub issues I never expect anyone else to read to help myself explore and verbalize a problem without having to nag anyone else about it; it’s been helpful and also yields a lot of what is effectively documentation of the “why” behind our design choices. Not sure if it would work as well on public repos or if you work with anyone that tries to max their GitHub stats (eg average issue close time) though.