How we behave here.
A short list. We're a community for reliability engineers, platform folks, and operators. Keep it useful, keep it respectful, and everyone has a better time.
-
1
No self-promo or vendor pitches.
If you're here to sell your tool, sponsor a newsletter, or funnel people to your cold-email sequence, this isn't the place. Share learnings and outcomes. If someone asks for a recommendation and your product fits, disclose your affiliation.
-
2
Be specific. Share numbers.
"Our p99 jumped from 180ms to 3.2s" is a post. "Monitoring is broken" is a vent. The former starts conversations, the latter doesn't. Numbers, timelines, and real traces beat generic hot takes every time.
-
3
Respect postmortems.
If someone shares an incident story, don't pile on with "you should have known better." The person posting already knows. Contribute what you would have done differently, then the next team avoids the same mistake.
-
4
Credit your sources.
If you're sharing a pattern you learned from a blog post, a talk, or another engineer, link to them. The people doing the original work deserve the credit, and readers can go deeper.
-
5
Disagree on content, never on people.
Call a take wrong. Call a pattern an anti-pattern. Don't call anyone stupid, junior, or any variation. Every engineer in this community has cleaned up a mess you haven't seen. Stay civil.
-
6
No confidential data.
Stack traces, config snippets, and architecture diagrams are great. Customer names, production secrets, internal hostnames, and anything under NDA, not great. Scrub before you post.
-
7
Use the Report button.
If something breaks these rules, flag it. A moderator will review. Don't litigate in the comments, the reply thread isn't a courtroom.