-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SF Jan 24 & 25 Rails Workshop at Pivotal Labs (@lilliealbert) #1
Comments
Emailed students to see if any repeat attendees wanted to help with check-ins. Friday: Stella C & Meredith T (Katherine M as relief help) And for posterity, here's what I wrote:
|
Emailed students to see if anyone beginners wanted to focus on Ruby instead of Rails on Saturday, with the plan to use Alex's Ruby curriculum . Students interested a Ruby section:
|
Friday schedule:
Saturday schedule:
|
Overall, this workshop went really smoothly. Pivotal Labs has pretty much the ideal space for a workshop. I forgot to initially confirm that they'd be paying for the food, so for future me: make sure to double check with hosts what they're going to pay for food so you don't have a few days of fear of fundraising :D I kept the student limit to 60 people until a few days prior to the workshop, then bumped it up to 72 to let in everyone from the waitlist. I never posted it to Meetup, but instead did outreach to some of the other communities I'm involved with (Dev Bootcamp women mailing list, Double Union). Plus lots of tweets on Twitter. I did email all the students who identified as male to ask who they were coming as the +1 of — most of the them wrote back immediately with the name of the person; I did get push back from one person and a non-response that turned into a no-show. (The person who pushed back on needing to be the guest of a woman immediately apologized, which was nice, but makes me think that we need to be enforcing that rule consistently.) Using Bridge Troll to do the class sorting was great; in the morning I ran around Pivotal and got the names of the conference rooms, then draw a rough map on the white board behind where I was giving the morning presentation. Having the names of the conference rooms + a map was invaluable in getting people into rooms. Since we were using Chaffee's Ruby curriculum, I emailed with students about a week ahead of time to see if anyone wanted to focus on Ruby instead of Rails. That worked out nicely. On Thursday evening, I sent all the students an email reiterating that they needed to download things BEFORE the Installfest on Friday. I don't remember hearing that the wifi really sucked at any point, so I'm gonna call that one a major success. I told Pivotal that we'd be having ~70 people, since I had about 90 people RSVP'd and figured there'd be some no shows. We definitely didn't have enough food for the 83 people that were actually there on Saturday, so I ordered some pizza at 12:15pm, as soon as I looked at the food we had. I think next time I'll just ask for as much food as we have people RSVPd, and not gamble with no-show rates. The pizza go there ~12:45pm, so it was pretty much fine, and nowhere near as bad as that time we got cold lasagna for 80 O_O. We're close to having a basic version of post-workshop surveys in Bridge Troll, but I think this time around I'm just going to send the Google form survey. I did have about 10 different people how they can find out about upcoming workshops, and since Bridge Troll doesn't have announcement capabilities yet, I told them to watch Bridge Troll :( Here are the notes from the student retro; they had great feedback & ideas: https://docs.google.com/document/d/1nAjYuuztC4FPInSStT6UGXZNL8K5NNzdAbZiq6Kc9s0/edit?usp=sharing |
Also for posterity, my email to students imploring them to download RailsInstaller or XCode prior to the Installfest:
|
Organizer: @lilliealbert
Venue: Pivotal Labs
Date: Jan 24/25
Curriculum: Rails
TODOS
The text was updated successfully, but these errors were encountered: