07 — Community

Build in the open

A working community rather than a chat room: questions get answers, projects get reviewed, and the archive stays useful a year later.

The rhythm

  1. Weekly

    Open thread

    One thread per practice area for work in progress. Post a diff, a stack trace or a design sketch and get a reading from someone outside your context.

  2. Monthly

    Challenge round

    A timed problem published on the first Monday, solutions unsealed at the end of the month, followed by a written review of the approaches that worked.

  3. Quarterly

    Build review

    Members present a finished project to a rotating panel: architecture, trade-offs, failure modes. Notes are published with the project.

  4. Always

    Q&A archive

    Focused questions with accepted answers, indexed across every technology area so the same problem is only solved from scratch once.

How we work together

Four expectations. They are short on purpose — everything else follows from them.

Get in touch
  • 01Ask with context: the code, the error, and what you already ruled out.
  • 02Review the work, never the person; point at the line, not the author.
  • 03Publish the reasoning behind a recommendation, not just the verdict.
  • 04Credit sources and prior work when you build on them.

Questions

Questions, answered

01How do I take part?

Build something, share the reasoning, and review someone else's work with the same care you want on yours.

02Is there a cost?

No. Participation is open; what it asks for is effort and good faith rather than a fee.

03How is feedback given?

Against the review criteria: specific, technical and about the work — never about the person.

04What is not tolerated?

Harassment, plagiarism and low-effort self-promotion. Those end participation.