Short version: be helpful, don’t post spoilers, don’t be a jerk.
1. Be decent to people. Disagree with ideas, not with humans. Criticize the approach, not the person who posted it. No insults, no harassment, no threats, no sexist/racist/exclusionary “jokes.” If you’re about to reply to someone’s tone instead of what they actually said, don’t post it, walk away instead.
This is a public forum and it’s indexed by search engines. Assume anyone could see it, including a future employer. Post like it.
2. Don’t post full solutions for live cases. This is the big one. Hints, approaches, relevant docs, “have you looked at X” all fine. The complete working answer to a graded Career or Assess task? No. It breaks the exercise for everyone who comes after you, and it undermines what a Praxicraft rank is supposed to mean. Full spoiler policy here.
If you are not sure whether something counts as a spoiler, it probably does. Ask in the thread before posting instead of finding out after.
3. Keep secrets secret. No API keys, no passwords, no Assess invite tokens, no private org content, no access tokens or session cookies, no unredacted screenshots or logs that expose personal or account data. If you’re pasting an error and it has a token or key in it, redact it first don’t rely on someone else to point it out.
4. Search before you post. Might already be answered. Two minutes of searching saves everyone time and keeps the forum useful instead of the same five questions on repeat every week. If you find a closely related topic, reply there instead of starting a new one.
5. One problem per topic, right channel. Makes it findable for the next person with the same issue.
| What you need | Where to go |
|---|---|
| Help with a skill/case | Help — SQL / Python / Linux / Airflow |
| Can’t log in, billing, account | In-app Support (not here these need private account details we can’t safely handle on a public forum) |
| Product idea | Feature requests |
| Something broken | Bugs & platform |
| Celebrating | Showcase |
If a reply sends the conversation somewhere new, start a fresh topic instead of hijacking the thread. Don’t post the same question in three categories hoping one sticks pick the right one and it’ll get seen.
6. If you’re asking for help, give us something to work with. “It’s not working” gets a slow, vague answer. This gets a fast one:
- What you were trying to do
- What you actually ran / clicked / typed
- What you expected to happen
- What actually happened, the real error text, not a paraphrase of it
- Which track/case/environment you’re in
Screenshots and pasted error text beat descriptions of them. If it’s a bug (not a “how do I” question), consider filing it directly in Bugs & platform instead of waiting for someone to notice it in a help thread.
7. Don’t spam AI-generated walls of text. Using AI to learn is fine, that’s kind of the point of a data eng learning platform. Pasting a generic AI answer you didn’t read, verify, or think about helps nobody, and it’s usually obvious. We want humans helping humans here. If AI helped you get to an answer, fine but write the reply like a person who understands it, not a copy-paste job.
8. Post your own stuff. Don’t post someone else’s paid content, another platform’s proprietary material, or methods for pirating anything. If you’re quoting docs or another source, link it and credit it.
9. If you see a problem, flag it, don’t fight it in the thread. Replying to bad behavior usually just prolongs it and buries the actual conversation. Flag the post and let a mod handle it. Moderators aren’t reading every post before it goes up, so flags are how the community actually polices itself not just something for staff to do.
Staff and mods will edit or remove posts that break these guidelines, and in serious or repeated cases, restrict forum access. Not personal just keeping the place useful for the next person who shows up stuck on the same problem you were.
One more thing
This forum exists because people practicing this stuff together learn faster than people practicing alone. Every thread you leave behind clear question, clean answer, no spoilers makes it a little easier for the next person. That’s the whole job.