Collaboration not Derision in the Node Community
strongloop.com
Collaboration not Derision in the Node Community
1–10 of 126 posts
Re: Collaboration not Derision in the Node Community
#2I think it was pretty classy of Ben not to comment on some of the hateful comments in the commit that, instead of adding to discussion or trying to prevent future error, simply were personal attacks at him.
Re: Collaboration not Derision in the Node Community
#3I love this post. I work with engineers on a daily basis and the one thing I find so foreign is an unhealthy attachment to perfection, as if such a thing existed. The easy thing to do is deride someone. The hard thing is to reach out. Nice article written in support of a hard working guy. Upvote.
Re: Collaboration not Derision in the Node Community
#4I think it was pretty classy of Ben not to comment on some of the hateful comments in the commit that, instead of adding to discussion or trying to prevent future error, simply were personal attacks at him.
I can't say I'm surprised though. bnoordhuis lacks tact; poke other people enough and eventually you'll get an angry mob. The parent article talks about learning, but glosses over that bnoordhuis' behaviour that set this all off isn't unusual for him. Learning? No. Class? No.
That said, this is a tempest in a teacup. bnoordhuis upsets someone again, news at 11.
Re: Collaboration not Derision in the Node Community
#5Most of the new guidelines[1] are technical, but the one relevant the events of the last day or two is on line 78:
+* When documenting APIs and/or source code, don't make assumptions or make
+ implications about race, gender, religion, political orientation or anything
+ else that isn't relevant to the project.
Re: Collaboration not Derision in the Node Community
#6I think the article is missing a lot of context. What was the offending issue?
Re: Collaboration not Derision in the Node Community
#7Did you send this as a private teaching moment first?
Re: Collaboration not Derision in the Node Community
#8> If Ben can’t learn, we’ll fire him.
That statement feels a little to intimate for an outsider to the company. Ben made a mistake but to single out and threaten him like that in public would surely alienate him further.
This entire situation has gotten extremely out of hand. It shows how activists can turn into extremists when faced with an adversary. I'm in no way advocating what Ben did but it's despicable how everyone jumped onto the bandwagon to exacerbate and publicize what should have been a minor event dealt with on employer-employee basis, not a public shaming.
Re: Collaboration not Derision in the Node Community
#9I think the community would do better without these corporate fingers poking on it.
Re: Collaboration not Derision in the Node Community
#10I think the article is missing a lot of context. What was the offending issue?
At a guess: https://github.com/joyent/libuv/pull/1015#issuecomment-29538... and
https://github.com/joyent/libuv/commit/804d40ee14dc0f82c482d...
Those two may not seem like much (at least I don't think so), but this kind of passive-aggressive behaviour isn't atypical for bnoordhuis. Eventually it'll cause a bad backlash. Like this.
bnoordhuis is an example of a problem that many popular OSS projects will face in their lifetime: is keeping a highly-productive jerk around worth it? On the one hand they produce good code, but on the other they help drag the community's ethos into the tank.