Community guidelines

• First-hand. You built it, ran it, broke it or fixed it. Say what you did, not what a vendor's page says.
• Specific. Versions, configuration, the exact error message, and numbers: how long it took, how much it cost, how big it got.
• Honest about what did not work. The dead ends are often the most useful part for the next person.
• Credited. Link the docs, issues and posts you learned from. Quote briefly and link; do not copy.
• Titled for what it is. “Cutting Postgres cold starts from 900 ms to 40 ms on Neon” beats “Some thoughts on databases”.

• Search first. If it has been answered, add to that thread instead.
• Say what you are trying to do, what you expected, and what happened instead.
• Include the exact error text, the versions involved, and the smallest code or config that reproduces it.
• List what you already tried, so nobody suggests it again.
• When an answer solves it, accept it. That is how the next person with the same problem finds the fix first.

• Answer the question that was asked, and explain why the fix works.
• Say so when you have not tested it, or when it depends on a version.
• Disagree with the idea, never the person.

Sharing your own project, article or product is welcome when the post stands on its own: what you built, how, and what you learned, not just a link and a call to action.

• Say when you work on, own or are paid by what you are writing about.
• Most of what you post should not be about your own products.
• Paid promotion that is not clearly labelled as sponsored is removed.

• Spam: link drops, repeated posts, and posts that exist only to send traffic somewhere else.
• Fake engagement: voting rings, second accounts, bought likes or follows, and asking people to upvote.
• Plagiarism: someone else's writing or code posted as your own.
• AI-generated content passed off as human: using a tool to help you write is fine, but a generated post presented as your own first-hand experience is not.
• Harassment: abuse, threats, hate, and publishing anyone's personal details.
• Anything harmful: malware, phishing, and illegal content.

Topic moderators remove what breaks their topic's rules; repeated or serious breaches of these guidelines can cost an account its access. Reporting from the site itself is coming. Until then, tell a topic's moderators or email support@dynamogeeks.com.