I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.

    • My first comment directly discusses the issue at hand. It wasn’t off topic. It’s clear you didn’t want any feedback on the issue because it makes you look bad. I explicitly talked about how client side scheduling is a bad idea that does not accomplish the goal of scheduling. And then I gave feedback directly concerning the exact issue I was commenting on of how your conduct was unfitting of lead devs of a major software project, where you squabbled in public in a really weird way, and you refused to even think about discussing the topic (closing the issue over and over again when your coworker had opened it and asked for discussion? Really dude?). Then you finally banned me without any warning or discussion of why.

      And no, it’s not going to teach me any lesson, all it did was teach the entire community you have no clue how to run an open source software project. No warning, no explanation, just juvenile marking of comments as off topic (they weren’t), closing of the issue your main dev opened and then boom banned.

      • This isnt the first time Nutomic has reacted in such a egotistical way, especially when someone points out a flaw in the software. I’ve seen a few issues that were actual issues with the software–not feature requests–that he’s closed and dismissed. One of the issues were mine. He definitely needs help with maintaining the software but I dont know how he expects anyone to help with the way he’s been acting.

      • My comment about scheduling in clients was from January and that option was already discarded by dessalines on the next day. No use in rehashing the same thing ten months later. All you are doing is creating pointless notifications for everyone. I know its not ideal to close and reopen an issue, but really why is it a big deal? We closed hundreds of issues recently which were outdated, invalid or already fixed. I accidentally closed one that still needs to be implemented and dessalines reopened it, so everything is fine. Certainly not a “squabble”, and your comments added nothing at all.

        Its true that I shouldnt have given a warning first, but most likely you would have responded with another offtopic complaint so I didnt see any use in that. If you want to complain then do it somewhere else, not on the issue tracker which is meant for getting work done.

        • Really? Is it necessary to ban people about making a valid argument. I know and also don’t like people asking a low effort “What’s the status of this” (and would totally get why such a thing would be marked off-topic, but a ban over something like this is still to harsh IMHO, they will learn, that such questions are not well-received over just the marking it as off-topic).

          But the comment discussed here has a valid concern (quickly closing issues that don’t have satisfactory solution yet, without getting feedback).

          A better reaction would be to just ask, whether the issue at hand is still relevant, having [these] alternatives at hand etc.

    •  Chefdano3   ( @Chefdano3@lemm.ee ) 
      link
      fedilink
      English
      4011 months ago

      You want to teach a lesson? The only lesson you’re teaching here is that you’re a twat. You get some hardheaded opinion on someone’s suggestion, refuse to listen to anything else, and ban them for explaining themselves. Grow up.

      • Yeah this guy is acting as if he’s a programming god who created something nobody could. This instance is called programming.dev, filled with programmers who know a little something about this programming thing. I’m a 15yoe self taught data engineer, and if I understand one thing, it is that anybody can learn programming and become great at it. I’m always proud of my code, but I never think my code is perfect. Programming and technology as a whole is constantly evolving, and what was clever/genius/wizardry yesterday is obsolete tomorrow. The only asset to a programmer is to be able to always learn new stuff, because there is always new stuff and better ways to do what you did in the past. I don’t even give detailed directions to my interns because I want to see if they do things in a different way that is better than the way I usually do things.

    •  millie   ( @millie@beehaw.org ) 
      link
      fedilink
      English
      7
      edit-2
      11 months ago

      Aggression and dishonesty aren’t going to help. You’d be better off dropping the defensive arguing and realizing that you overreacted. It’s okay to have screwed something up and admit it. You’d be getting a much better reaction if your response was along the lines of ‘Whoops, yep. Guess I’m a bit of a hot-head sometimes, I’ll try to look out for that.’

      But when someone literally can’t ever admit that they could possibly be wrong, that they could possibly have overreacted in any way, how is anyone supposed to work with that?

      Everyone is wrong sometimes. Being intractable about it doesn’t get you anywhere.