I think Recurse Center did a great job on these.<p>A lot of documents like this leave a lot to interpretation, and some of that is unavoidable, but I think this document does about as good a job as you can of making bad behaviors easy to recognize and avoid.<p>I also attended a Recurse talk, and they prefaced the Q&A with a rule I found helpful:<p>><i>Before you ask your question, think about whether it's a real question or just something you want to say in front of the speaker. If it's just something you want to say, approach the speaker afterwards and tell them privately, and reserve the questions for things other people might want to ask as well.</i>
As a Recurse Center participant and alum, these rules form an important and largely silent backbone of the community's culture.<p>Often reading rules causes strong reactions. Seeing how those same rules are implemented makes all the difference.<p>Rather than discussing the rules, I'll share experiential evidence: the community is welcoming to beginners, gentle, curious, kind, playful, and above all else: supportive.<p>The rules are a helpful "buck" to stop at should mistakes or conflict - small or large - arise (which rarely occurs). The key is commentary and forgiveness.<p>The experience of attending a batch at recurse is largely regarded as their best for many of my fellow Recursers - it certainly is one of mine.<p>If you're curious please reach out to them. I'm also happy to chat or answer any questions (and give a glowing review).
I would like to see a 5th rule: Don't assume a question is an X/Y Problem just because you lack context.<p>Because this happens basically every single time a ask a question online without including a doctoral thesis on my project's history, constraints and goals.