Discourse
Community.
We're trying to build the comments section the field deserves — technical, kind, signal-rich. The discussion lives on GitHub and Discord, not here. No karma, no algorithm, no ads.
GitHub Discussions
asynchronousLong-form Q&A, paper threads, RFCs. Tied to your GitHub identity — searchable, attributed, permanent.
Open DiscussionsDiscord
real-timeReal-time chat for the working day. Quick questions, debugging help, paper club, off-topic.
Join the serverGitHub Issues
bug reportsFound a bug on the site, a broken link, or a typo in an article? File it on the repo.
Report an issueX / Twitter
announcementsNew articles, threads, and announcements. Follow for the firehose.
@MLSystemsDevHouse rules
- Be specific. Vague questions get vague answers.
- Show your numbers. Benchmarks beat opinions.
- Cite, don't paraphrase. Link to the paper, the commit, the issue.
- Disagree on substance, never on identity.
- Help juniors. We were all juniors yesterday.