Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
Founded in 2002, Seattle.rb is the first and oldest ruby group in the world. We've evolved a lot over the years and have found a balance that I think works very well for many, if not most, groups. Seattle.rb has also had a study group off-and-on for a few years. We've tackled doozies like SICP but also programmed games in Racket (scheme). I will share the recipe for our user group and study group as well as the trade-offs we've made over the years and what they meant to us. Help us caption & translate this video! http://amara.org/v/FG2N/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In his talk titled "Nerd Party, v3.1" at the MountainWest RubyConf 2014, Ryan Davis discusses the evolution and dynamics of user groups, particularly focusing on Seattle.rb, the oldest Ruby group in the world, which he co-founded in 2002. The main theme of the presentation is to share insights and best practices for running successful user and study groups based on his experience with Seattle.rb. Key Points Discussed: - **Group Evolution**: Ryan categorizes the evolution of Seattle.rb into three main stages: - Version 1.0 (Plain Vanilla Meetup): Monthly meetings with inconsistent locations, leading to challenges in organization and speaker recruitment. - Version 2.0 (Nerd Party Era): Transition to weekly, informal hacking sessions at a consistent cafe, fostering a more relaxed and accessible environment. - Version 3.0 (Nerd Party Plus Monthly Social): A hybrid model combining weekly meetups with monthly social events that incorporate talks, increasing engagement and attracting a wider audience. - Version 3.1 introduces study groups that meet weekly prior to regular sessions, focusing on challenging programming materials to deepen participant knowledge. - **Importance of Structure and Accessibility**: Davis emphasizes the value of having a consistent meeting structure and location, which enhances attendance and participation. He also discusses the balance between structure and flexibility to cater to various participant needs. - **Case Studies and Anecdotes**: Ryan shares stories about individuals inspired by CLRB's format, such as the creation of the Fraser Valley Ruby Brigade by a Canadian attendee, which highlights the impact of sharing effective practices. He also refers to the establishment of local groups in San Francisco that aimed for a similar informal style. - **Community Engagement**: Successful groups cultivate an environment that encourages contributions from all members. Davis encourages hosting varied events like hack nights and 'show-and-tell' sessions to promote engagement. - **Learning Materials**: He advocates for selecting challenging books for study groups, sharing details of works such as 'Structure and Interpretation of Computer Programs' (SICP) and 'Realm of Racket', which help participants solidify their programming skills through hands-on projects. Conclusions/Takeaways: - Groups should establish their identity, catering to the interests of their members while promoting engagement. - Using local resources such as mailing lists for coordination is crucial for maintaining communication and involvement. - The evolution of user groups can lead to richer learning experiences, as demonstrated through the various formats and structures employed by Seattle.rb. Overall, the insights shared by Ryan serve to guide others in building and enhancing their own tech communities effectively.
Suggest modifications
Cancel
