A reawakening of systems programming meetups

Original Article ↗ Hacker News Discussion ↗

Enthusiasm for systems and programming meetups is returning in some cities, but organizers and attendees are wary of repeating pre-pandemic pitfalls like devrel product pitches, resume-padding talks, and job-market-driven self-promotion. Commenters describe how venue costs, corporate dependence, and the decline of platforms like Meetup.com have hollowed out many local tech communities, and share tactics that work better: strict curation of talks, requiring prior attendance before speaking, favoring deeply technical content, and leveraging universities, libraries, makerspaces, or community centers. There is broad support for meetups that prioritize genuine knowledge sharing and local networking, even if that means smaller events or more work for volunteers.

Commercialization and DevRel Fatigue

  • Many report pre‑pandemic meetups devolving into thinly veiled product pitches and resume-padding talks.
  • Complaints include: devrel talks focused on tools/coins/ICOs, minimal technical depth, speakers leaving immediately after, and insisting on video for personal branding.
  • This behavior is seen as turning attendees into “props,” causing core communities to drift away.

Curation, Talk Quality, and Ground Rules

  • Suggested countermeasures:
    • Require speakers to have attended several meetings first.
    • Forbid employer/product mentions beyond an intro slide.
    • Avoid topics with high “grift” density (e.g., some JS/TS, crypto).
  • Others argue such rules would make it too hard to recruit good speakers; high‑quality talks are inherently a form of marketing (for teams, hiring, reputation) and that’s acceptable if the content is substantial.
  • Consensus: technical depth and relevance must dominate; brief, non-pushy plugs are fine.

Venues, Sponsorship, and Costs

  • Persistent pain points: finding stable, free/cheap venues; organizer burnout; and liability/insurance requirements.
  • Corporate venues can vanish with internal politics, or add friction via security, badges, and NDAs.
  • Alternatives used: libraries, makerspaces, hackerspaces, community centers, co‑working spaces, universities, bars/cafes. Noise, hours, and accessibility (including for people with hearing loss) matter.
  • Debate on public funding: some argue municipalities should provide free meeting space as civic infrastructure; others question why all taxpayers should subsidize niche groups.

Role of Universities and Public Institutions

  • Some are surprised more universities don’t host public tech events; concerns include brand misuse and grifters claiming affiliation.
  • Examples given of student-led clubs and database groups at universities that successfully host technical meetups with filters (paper forms, campus location, technical talk guidelines).

Platforms and Discovery

  • Meetup.com is widely seen as worsened by ownership changes and pricing; activity in many cities reportedly declined before COVID.
  • Alternatives mentioned include federated tools (e.g., Mobilizon) and new meetup-like services.

Local Scenes and Revival Efforts

  • Reports of both dead and reviving scenes in cities like Portland, SF Bay, NYC, Boston, London, LA, Phoenix, Chicago, Toronto.
  • Formats that work well: paper-reading groups, deeply technical systems/database talks, casual hack nights, and hybrid in‑person/Zoom setups.