Code of Conduct.
A small community of senior engineers can only stay valuable if its norms are explicit. These principles cover three domains — how we use AI, how we write code together, and how we treat each other as humans. Membership implies agreement.
On AI.
How we use cognitive engines responsibly, and what we expect of one another.
Be explicit about AI involvement.
When you share a workflow, an artifact, or a recommendation in the community, name the model, the prompt strategy, and the human review you applied. Hidden AI usage erodes trust faster than any single mistake. We're not here to pretend we're smarter than we are; we're here to compound what works.
Cite, test, and audit before you ship.
Generated code, generated docs, generated recommendations — none of them get a pass. The person who runs the prompt owns the output. If you cannot defend a line in code review, do not paste it into production. The same applies to claims you bring into the channel.
Mitigate vendor lock-in by default.
A community member should be able to swap providers without rewriting a system. Design for multi-model routing where it matters. Prefer open weights where licensing and quality allow it. We don't fight provider wars; we keep optionality alive.
Respect what is not yours to share.
Do not pipe client code, customer data, or non-public organizational information through any model — frontier, hosted, or otherwise — without explicit authorization. When in doubt, anonymize, abstract, or ask the channel before you ask the model.
On development.
How we ship software so the next engineer — or agent — can pick up the thread.
Specification leads. Implementation follows.
We architect, then we generate. The contract — interfaces, invariants, business rules — is the human's job. Boilerplate is the model's job. Reversing that order produces fragile systems and bored engineers.
Code is read more than it is written.
Vibe-coding is a velocity multiplier, not a license. Generated code that no one understands six weeks later is a liability. Audit ruthlessly. Document intent, not syntax. Leave the codebase friendlier than you found it.
Reach for the simplest tool that suffices.
An autonomous multi-agent swarm is not the answer to a problem a 40-line script would solve. Complexity is a tax paid every time someone re-enters the system. Pay it only when the value is clear.
Test business logic, not implementation.
Bring evals, benchmarks, and reproductions. Anecdotes are welcome as a starting point; they don't end a discussion. When the room disagrees, the artifact wins.
On life.
How we treat each other inside the channel, and outside it.
Senior does not mean dismissive.
We are a community of experienced engineers. Experience is no excuse for condescension. Disagree on the substance; never on the person. As we open to less senior peers — model the room you want them to enter.
Share the breakthrough you didn't have to share.
If you cracked something this month, post it. Even rough notes. The community's value compounds on members who give before they take. Lurking is fine in busy weeks; permanent lurking is not.
What's shared in the channel, stays in the channel.
Do not screenshot, quote, or attribute another member's posts outside the community without permission. Ideas can travel; specific words and names cannot. This is the foundation of candor.
No recruiting, no selling, no pitching.
This is not a sales channel. Job opportunities and collaborations happen — in DMs, between members, when both sides want them. Mass outreach, vendor pitches, or product placement gets removed once and warned twice.
Protect your attention.
The frontier moves every week. The community exists so you don't have to chase all of it alone. Use the channel as leverage, not as another inbox. Mute aggressively, focus deliberately, and step away when you need to.
How we handle violations.
Any founding member can raise a concern directly with the involved party or anonymously to a moderator. We assume good faith first, and we resolve in DMs whenever possible.
Repeat or severe violations are reviewed by three founding members. Outcomes range from a private warning to immediate removal from the community. We document. We do not litigate publicly.
Report concerns to conduct@aicodingeesti.ee. All reports are confidential. We will not retaliate, and we will not name reporters without permission.