from Hacker News

Misunderstanding professionalism and the new Ruby code of [mis]conduct

by tripu on 10/4/21, 8:45 AM with 4 comments

• by raxxorrax on 10/4/21, 11:20 AM

  Fully agree with this assessment. Problem is that this now creates extremely destructive atmospheres. Honestly the authors of the correction should be ashamed of themselves.

  Every set of rules will contain mistakes but the consistency of bad ideas is concerning.

  I believe the synopsis will hold though, shining light on it will solve it eventually, even if there are still a lot of biased views in media especially.

• by ghoward on 10/4/21, 8:37 PM

  Avoiding things like this is the reason I don't have any Code of Conduct for my public FOSS projects. [1]

  The flip side of that is that people need to trust my vision for culture [2] and trust me to do the right thing to build that culture. And of course, I need to vindicate that trust.

  There will be plenty of people who don't trust the vision or me, and that's fine. In fact, that's an expression of a free market for ideas, so I want people to be able to choose.

  [1]: https://gavinhoward.com/2018/11/code-of-conduct-for-yzena/

  [2]: https://gavinhoward.com/2021/09/comments-on-cosmopolitan-and...

• by aaron-santos on 10/4/21, 4:06 PM

  What a weird section on professionalism. The social construct of professionalism re-enforces the neoliberal hegemony. Who the hell would want to do that?