Ruby Podcast Panel
summary
Panelists give concrete tactics and outcomes: a podcast wraps up after 52 episodes, sponsors include Honeybadger and Judo Scale and Go Rails, inviting guests reliably starts conversations and seeds future referrals, board game night demonstrably lowers social anxiety and generates meetups, hack day work even closed an issue on Factory Bot in person, Hotwire/Turbo/Stimulus get named as the front‑end direction people want to try, and active_resource is cited as a concrete feature that didn’t survive real‑world use.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 2:34Networking at conferences
- 6:25Podcast guests pros and cons
- 11:02Attracting Ruby programmers
- 17:20Favorite conference memories
- 25:30Improving Rails ideas
- 32:08How podcasts began and first episodes
- 38:53Getting podcast guests
- 44:37Fresh podcast content
- 47:24Influential guests
- 51:01Closing remarks
