3 ms·
If I go to an interview for a Python developer position, and I say "I think Python is a stupid language and nobody should use it," and I don't get the job, it w
by geofft 9y ago
If I go to an interview for a Python developer position, and I say "I think Python is a stupid language and nobody should use it," and I don't get the job, it would be ridiculous for anyone to say that I got punished for not using the correct words.
This is the same thing. The Node.js TSC is the body that maintains and enforces the Code of Conduct. Maybe Node should have a CoC, maybe not, but so long as it has one, the body that enforces the CoC should actually intend to enforce the CoC. If they don't want it - get rid of it! Lots of projects don't have one. But if they want it, certainly only people who actually intend to enforce the CoC should be enforcing the CoC.
- syshum 9y ago>>If I go to an interview for a Python developer position, and I say "I think Python is a stupid language and nobody should use it," and I don't get the job, it would be ridiculous for anyone to say that I got punished for not using the correct words. This is a terrible analogy and in no way related to the topic at hand. I am not even going to bother to refute it as it should be obvious as to why this analogy is flawed >>This is the same thing. The Node.js TSC is the body that maintains and enforces the Code of Conduct. the TSC seems to believe this was not a violation, and upon reading what the person is accused of, and the CoC I agree it is not a violation of their codes. Now it seems some in the project want to adopt even more restrictive CoC to further police any members actions even well beyond anything that is even connected with Node Development, that is insane
- deleted 9y ago[deleted]
- scubapilot 9y agoLet me stretch your analogy to make the opposite point: I am employed as an embedded developer. The position I was hired for has a heavy focus on C programming. I would never write the "C is stupid and nobody should use it anymore" articles, but I do still think they have merit and will share them around the company. As someone who knows how to read an argument and separate wheat from the chaff, I have been experimenting with Rust and raising the possibility of adoption in certain areas of new development. I do not intend to write C at this job. I intend to leverage the right tools to achieve our embedded goals. For as long as that means C, it'll be C, but C might not be the most appropriate tool and I am open to changing our tools.
- fixermark 9y agoReally, the language- or framework-based examples don't apply well because people aren't tools. CoCs generally protect people from bad behavior by other people, under the assumption that debating the merits of people the way you'd debate the merits of tools is, well, a dick move.
- scubapilot 9y agoI agree, people are not tools. But codes of conduct are tools. They are used by people, to achieve goals.
- geofft 9y agoYes, and I think that's fine. (I'm in a largely similar position in my own job as it happens, and my management agrees: we probably want out of the technology I'm working on, but we want it well-maintained until we figure out what our better option is.) My sense, and again I am an outsider and might be wrong, is that Rod wasn't of the opinion that he'll enforce the CoC as long as the TSC (other smart people) and the Node community see it as the right current plan, but he'll advocate for long-term change. He was of the opinion that, right now, not only was the CoC without merit, but it's reasonable for him to actively apologize for moderation actions that the rest of the TSC took. That is I think not directly analogous to what you are doing. It is much more analogous to you replying to your coworkers code reviews with "-1, it's 2017, you shouldn't write in C," or replying to your customers' bug reports with "Yeah, well, we're writing in C so of course our code is broken." Your coworkers are willing to work with you because they believe, regardless of what articles you're sharing, that for the foreseeable future you will write the best C you can and help them write the best C they can. If that trust is there, advocating for change is totally reasonable. If it's not, and either you believe that your coworkers are hopelessly misguided or they believe that you're hopelessly misguided, one of the two factions needs to leave for the team to be productive again.
- smsm42 9y ago> "I think Python is a stupid language and nobody should use it," And if you say "there can be downsides to using Python, here's an article describing them" and the response is "you're fired, you infidel, how dare you to question The Sacredness!" then I probably don't want to work in that company.
- geofft 9y agoI agree, but I'm not sure how that's relevant.
- smsm42 9y agoThat's pretty much what happened to nodejs, as far as I can see - somebody said that CoC and speech codes may have downsides, people freaked out and demanded that either he's booted out or they leave.
- geofft 9y agoI am not a Node community member so my knowledge is limited, but that seems like an oversimplification for two reasons: one, he is on the team charged with upholding the CoC, and two, he apologized for the work his teammates did to uphold the CoC.
- smsm42 9y agoWhat is wrong with considering downsides of CoC while enforcing it? I'd say that exactly what person charged with enforcing it should be doing, and if they refuse to even admit the thought there might be any and haven't discussed them before, they may not be ready to enforce it properly. Reevaluating the premises and ensuring that upsides of the current rules exceed downsides, and challenging them if they do not, is the part of a healthy governance process, and flipping out at the mere thought of it is not a sign of a healthy one. Imagine a judge that is sure there's never downsides and unintended consequences of any law, and never admits a thought that the application of law can be unjust or hurt somebody. Wouldn't you be scared of such Judge Dredd?