Discussions
Open to all membersTopic threads on architecture, tooling and the parts of a path people get stuck on.
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.
- Spaces
- 5
- Review cadence
- Quarterly
- Challenges
- Monthly
- Archive
- Searchable
Challenges
MonthlyTimed problems with published solutions and a written review after each round.
Events
ScheduledWorkshops and walkthroughs run by members, recorded and archived.
Project Showcase
Peer reviewedPost what you built, get structured feedback on code, docs and decisions.
Q&A
Searchable archiveFocused questions with accepted answers, searchable across every topic area.
The rhythm
- 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.
- 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.
- Quarterly
Build review
Members present a finished project to a rotating panel: architecture, trade-offs, failure modes. Notes are published with the project.
- 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.