Conference‑Driven Development: Discovery Engines or Disappointing Disa...
summary
Claim: use CFP deadlines as structured R&D sprints so teams submit→prototype→feedback→release→present within a conference cycle. Workflow maps ambition, transparency and program integrity and proposes guardrails like pre-conf artifact pledge and a fallback “lessons learned” narrative. Concrete examples include integrating Guac and Zarf as a conference-forced project and a Flux Con proposal that stalls when not accepted. Review risks include bias toward mature repos, security concerns for low-star projects, and practical tradeoffs between rapid prototyping and reviewability.
AI-written summary · about
chapters (11)
- 0:00Conference-driven development
- 1:28Attendees return to CubeCon
- 4:18Mentorship and community growth
- 5:20Reviewing talk proposals
- 8:09Standout talk submissions
- 10:39Innovation versus feasibility
- 12:49Core idea of conference-driven development
- 17:23Embracing failure in talks
- 21:17Breaking bottlenecks
- 22:20Real-world conference-driven examples
- 24:27Q&A on track relevance
related talks
01mClosing Remarks
02mit's all about the people
33mSharing is Caring: How to Begin Speaking at Conferences
16mSummary & Outlook
34mUnconference Session: The Happy Circle: Maintainers and End Users
22mPanel Discussion: The 5 Ws and...
02mRecap
14mThe AST CASTcast: Episode 17: Developing the Conference Theme