4 ms·
I've always felt that codes of conduct came from HR people who can't program but want to contribute to a project. > [F]rom a European perspective, it looks lik
by maxlybbert 10y ago
I've always felt that codes of conduct came from HR people who can't program but want to contribute to a project.
> [F]rom a European perspective, it looks like such an American thing to do. You need written rules for everything.
Years ago, while playing with the family at a lake, I noticed one of our inflatable water toys had different warnings next to different flags. Yes, many were in different languages, but there were at least three English warnings on there. The British and Australian warnings were just "use under competent supervision." The American warning was a couple paragraphs long, and very detailed: "do not use while drunk; do not tow from boat; do not dive into; ..." I was embarrassed as an American.
- johnny22 10y agoyou felt wrong. I write programs, but also add CoCs if there's more than a few folks are contributing.
- deleted 10y ago[deleted]
- maxlybbert 10y agoI recognize that not everyone recommending codes of conduct literally comes from human resources, but it's the simplest way I can understand why somebody would say "what this project needs is a document defining good and bad behavior." Perhaps it's just a personal hang-up. I believe some style guides are worthwhile, and style guides could be described as documents describing good and bad design or good and bad code.