My upcoming speaking events
I had a blast speaking at the Database meet-up that Wellness FX put on last month where I talked about managing migrations in Mongo. I’m pumped to follow that up with speaking at Madison Ruby this coming week-end where I will be expanding the material from that initial 20 minute talk to the fuller 30 minutes allotted at Madison. I’ll definitely be fleshing out some of the positives of working with MongoMapper that I glossed over in the initial talk - namely the incredibly fun power of the DataMapper pattern combined with a schemaless datastore. Hopefully this helps alleviate some of the anti-Mongo vibe my first talk seemed to give off; MongoHQ are speaking at Madison as well and we wouldn’t want that to lead to a pub brawl during the post conference drinking (we’re rubyists, the drinking is a given). Don’t worry though, I won’t let that entirely keep me from speaking my mind. ;)
Next I’m organizing a panel on hiring rubyists, coming up in Sept, with some very well known names in the local ruby community. I’m honored that they all seemed to jump at the chance to do this panel with me. As a consultant, how to deal with hiring rubyists is a question that comes up constantly and it will be great to get these 4 views on the topic posted up on the web so I can point to it and say “that’s how.” I definitely have to say thank you to Engine Yard for graciously offering to host the event.
And to cap off my continuously expanding talk on Mongo and how to deal with your lack of schema, data validity, migrations, etc, I will literally be closing down the conference at RubyConf. I’m hoping that even though I am speaking dead last, my immediately following Tom Preston-Werner will help motivate attendees to stay to the bitter end for my talk. I will have already added some code examples to my nearly Bauhausian minimilist slides from the Wellness event for Madison, but talks are 45 minutes at RubyConf, so there will certainly be even more of the nitty gritty and code examples that people have been asking for.