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.

Page objects are the best things to happen to my cuking. Step definitions are a couple of lines at best and I'm dealing with a real Ruby object instead of some node from Capybara. I'm excited about Cucumber again.

All great points, but I take offense to the shots at responsive frameworks. There's still learning that has to happen there from developers. Grids are powerful and learning to work within frameworks instead of against them is a very important step that many people often ignore.

This is video from our last Cincinnati Ruby Brigade. The topic was memory management including background, strategies and how it applies to Ruby development with the MRI.

We're not SF. We'll never be SF and that's just fine. We have a vibrant and enthusiastic tech community here in Cincinnati. We have a great city that's doing all the right things to attract and retain talent, too.

If there's one thing we're doing poorly, it's making those points known. After Queen City Merge, we started working on Made In Cincy to create a unified presence of tech startups, agencies and individuals. We're out here, doing good work every day.

I bought this book and will happily buy the next one if you'll cover the process of slicing that PSD and converting it to HTML. I'm capable, but I always feeling like I'm working too hard when I do it. I'd just like to see how a professional does it, I guess.

Or if you know of a resource that details this process, I'd read that, too.

cit is another favorite. Try it inside HTML tags, for example.

So far, it looks like the only real differences are:

* jammit uses config/assets.yml, sprockets uses inline requires

* jammit loads individual files in development, sprockets concatenates

* sprockets compiles coffee with :bare => false by default. I don't know what barista's default is

Felt it in Cincinnati, OH, too.

lsof

Lots: http://github.com/cdmwebs/dotfiles/raw/master/vimrc

Probably time to clean it up a bit.

Same experience here. I got the forwarding working, but the callback from GV to the iPhone is pretty frustrating.

Or this: http://www.google.com/support/forum/p/voice/thread?tid=56a63...

Actually, it did reset to AT&T. I tried a few of these playing around.

So ##002# will cancel and return to AT&T VM?