Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Jul 8, 2013
In the second half of 2012 I "quit my job" as a traditional Ruby/Rails consultant in order to become a consulting pair programmer. After spending hundreds of hours pairing with dozens of developers from around the world, I'd like to share some of my observations. We'll talk about the mechanics of ad-hoc remote pair-programming, but more importantly about why I think widespread pairing is important to maintaining the health of the Ruby community. Whether you work solo or you pair regularly, you should leave this talk empowered and excited to broaden your pair-programming horizons.