Charles and Brandon argue about what to name the podcast.
They talk about how "one more feature"-itis sinks many projects and startups, how you can recognize when you're caught in it, and patterns they've used to avoid it.

Charles and Brandon argue about what to name the podcast.
They talk about how "one more feature"-itis sinks many projects and startups, how you can recognize when you're caught in it, and patterns they've used to avoid it.

Charles and Brandon argue about what to name the podcast.
They talk about how "one more feature"-itis sinks many projects and startups, how you can recognize when you're caught in it, and patterns they've used to avoid it.

Charles and Brandon argue about what to name the podcast.
They talk about how "one more feature"-itis sinks many projects and startups, how you can recognize when you're caught in it, and patterns they've used to avoid it.

Charles and Brandon argue about what to name the podcast.
They talk about how "one more feature"-itis sinks many projects and startups, how you can recognize when you're caught in it, and patterns they've used to avoid it.

If you work in Rails and have ever wondered about Ember.js, you should know that Ember and Rails go together like Nutella and pretzels. (Which is to say, quite well indeed.)

Get an inside look of the experience of going from having never tried Ember to shipping a production application in it. What makes Ember a good match for certain types of applications?

It began during RailsConf.

My fingers were itching to code, so between sessions I started
tinkering with some of the more fanciful enhancements to
The Ruby Racer I’d been contemplating as well as wrestling with
a number of long-standing bugs. But what started out as a small
refactoring slowly but relentlessly gained momentum until things
were completely out of control.

In which I elaborate why the idomatic Ruby API is sometimes not enough,
and describe a method to harness the full power of the underlying
Jenkins API while still happily coding your extension in Ruby

To quote Dave Bowman, “something wonderful happened” last week during the weekly Jenkins-Ruby hack session.

In which I explain problems unique to running The Ruby Racer in a multithreaded environment,
which users are affected by these problems, and what is to be done for them.

UPDATE: This issue has been resolved with version 0.9.1.
You should be able to stop reading here, update your Gemfile, and have a great day. That said, please don’t
let me discourage you from continuing down the page. It’s riveting.