cdmwebs

This is the first part of a series. Here are the other posts:

http://jeffmason.me/rails-phoenix-live-polling-part-1/ http://jeffmason.me/rails-phoenix-live-polling-part-2/ http://jeffmason.me/rails-phoenix-live-polling-part-3/

This is where tools like https://www.nitrous.io are awesome. We just hosted a RailsBridge-type event and we used Nitrous. Highly recommend this for teaching.

Nice! Open sourcing this is a great idea, Emerson.

Nope, that's it. We do have experimental internal apps we build in other languages, but most of our work is Rails apps.

Because of the reasons in the post, but mainly our design team. I didn't want to set up a WordPress instance and make them learn the intricacies of php and WP theme system. They already understand the Rails folder structure, Sass, Haml and all the other tools we use.

tl;dr: it made collaboration easier.

It's painful. I hoped that an engine existed, but nothing fit our workflow. This seems like a good starting point, though. Maybe we'll convert to an engine and see how reusable it might be.

I used errbit for a while and it was losing stacktraces ;(. Wound up using https://github.com/getsentry/sentry and am much happier.

QCMerge is intentionally different than most conferences. We don't focus on a particular language or framework. It's about everything that goes into building a successful product.

The observations in the article are things we noticed after two years of the event. We didn't set out to "attract more women," but rather to attract more people.

This is a struggle, for sure. We want to keep them consistent but we also want to make sure we're keeping things moving. They shouldn't be a checklist, but actual features, too. Timeboxing work is the only workable solution I can see.