What I Have to Do at OdessaJS Conference
summary
Advice for conference attendees on maximizing value at OdessaJS: prioritize meeting people and getting feedback over attending every session, pick four talks to focus on, skip others, and use corridors, speaker-corner slots, and afterparties for direct feedback and relationship-building. Provides concrete regional attendance data (Odessa grew from ~60 to 250 events; ~4,000 unique attendees total) and highlights technical topics to watch such as framework-agnostic microservices to serverless and TypeScript migration strategies.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 1:50Attendee problems
- 3:14Audience levels
- 4:59Talk goals
- 5:42What is community
- 7:48Community in jobs
- 9:18Openness in community
- 11:26Tech choice mistakes
- 12:52Development trends
- 14:36Community relationships
- 15:21Talk burnout
- 16:28Feedback to speakers
- 17:32Asking questions
- 18:38Q&A
- 19:42Conference growth
- 20:47Community growth
- 21:28Conclusion
