That's only a correlation though; it seems just as likely that communities that already have low tolerance for negative behaviours are also quicker to add a code of conduct.
That second link does make some good points that seem to apply mostly to businesses, but fall apart in the context of smaller open source projects, specially the legal aspect of it (which is also very specific to the USA). Most projects also just use an unmodified, widely used COC like the contributor covenant, meaning it doesn't signal anything to a would-be contributor other than a binary "has COC" vs. "has no COC".
Last but not least, a COC would be useless without a community that actively complies with it, in which case this community in itself would be a much stronger signal (think looking at code vs. looking at documentation).
Considering those points, I'm still very sceptical of the effectiveness of having a dedicated "be nice" document as part of the project. It seems more like the main reason to have one is the relatively small effort of throwing one in the repo regardless of how useful it may be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's only a correlation though; it seems just as likely that communities that already have low tolerance for negative behaviours are also quicker to add a code of conduct.
That second link does make some good points that seem to apply mostly to businesses, but fall apart in the context of smaller open source projects, specially the legal aspect of it (which is also very specific to the USA). Most projects also just use an unmodified, widely used COC like the contributor covenant, meaning it doesn't signal anything to a would-be contributor other than a binary "has COC" vs. "has no COC".
Last but not least, a COC would be useless without a community that actively complies with it, in which case this community in itself would be a much stronger signal (think looking at code vs. looking at documentation).
Considering those points, I'm still very sceptical of the effectiveness of having a dedicated "be nice" document as part of the project. It seems more like the main reason to have one is the relatively small effort of throwing one in the repo regardless of how useful it may be.