Community guidelines

• Critique code, not people. Beginners and AI-assisted builders are welcome.
• No harassment, discrimination, threats or personal attacks — in public posts or private messages.
• Assume good faith and explain the “why” behind a fix so others learn.

• Describe what you expected, what actually happened, and the exact error message.
• Share a minimal snippet that reproduces the problem — not your whole codebase.
• Say which tools, frameworks and versions you use, including any AI coding tools.
• Test proposed fixes yourself and give honest feedback with “Accept” or “Didn't work”.

Need a private review of a full project? Use software validation instead of posting code publicly.

• Explain the root cause and how your change fixes it.
• Describe how you tested it. Untested guesses should be comments, not solutions.
• If you used an AI tool to draft an answer, verify it yourself and say so.
• Don't copy others' work without credit, and don't post the same answer across many problems.

Reputation is awarded only when the person who asked accepts a solution and records how they tested it. Every award is visible on the contributor's profile as evidence.

• No vote trading, sock-puppet accounts or accepting answers from friends who didn't solve the problem.
• Moderators may reverse reputation gained through manipulation and record a visible correction.
• Levels 4–6 require review by the platform; a high score alone never grants reviewer or paid-work status.
• Reputation does not guarantee employment or income.

• Never post API keys, passwords, tokens, private keys, connection strings or customer data.
• If you spot exposed secrets in someone's post, report it so a moderator can remove it — and tell the author to rotate them.
• Validation files are private to the owner and assigned reviewer. Don't share them outside the platform.
• Only submit code you have the right to share.

• Malware, exploits aimed at systems you don't own, or help bypassing security you aren't authorized to test.
• Spam, advertising, link farming or off-platform payment requests in public posts.
• Requests to do unpaid commercial work disguised as a community problem.
• Illegal content or anything that violates others' privacy or intellectual property.

• Reviewers only accept cases within their verified expertise. A strong programmer isn't automatically qualified to review, for example, tax or accounting logic.
• Every finding needs evidence and a recommendation. Preliminary or automated findings must be confirmed by the reviewer.
• Reports state the scope, version, methods and limitations, and never claim software is completely secure, bug-free or legally compliant.

Use the Report link on any problem, solution, comment or profile. Moderators review every report and may remove content, correct reputation or suspend accounts. Suspended members are notified and can appeal through contact & support.

Helping in the community is always voluntary and free. When paid assignments become available, each will state its scope, deliverables, deadline, payment terms and acceptance criteria before anyone accepts it. Keeping your rank never requires unpaid commercial work.