Seriously though, this book has taken much longer than intended, partly as the scope grew, but mostly because of other projects getting in the way. Such as the launch of RubyTapas. I’m hugely appreciative of all the early-access buyers who supported the project and have been patient through this process.

Those early buyers have already heard the news, but now I’m letting the rest of the world know: as of now, Confident Ruby is finally content-complete and entering a Beta phase. That means that while there is plenty of editing, clean-up, and tweaking to do, all the major content (a little over 150 pages’ worth) is now in place.

I intend to spend one month getting Confident Ruby into shape for a final release. At the end of that month, I will be raising the price to $35. Until then, you can still get it for $25. As always, if you don’t have the scratch you can send me a postcard instead.

Curious about what’s inside? The nutshell version is that this is a patterns book, focused on the method level of code. It’s all about how to make methods that are “confident”: that is, they tell a clear, straightforward story without a lot of distracting provisos and digressions. In order to get you from “timid” code to confident code, I lay out 32 patterns for collecting input, delivering output, and handling failure within a method. There’s a strong emphasis throughout on removing the scourge of nil values from code, and replacing them with more semantically meaningful constructs.

Here’s the current table of contents, if you’re curious:

• Introduction
  • Ruby meets the real world
  • Confident code
  • A good story, poorly told
  • Code as narrative
  • The four parts of a method
  • 3.times { rejoice! }
  • Collecting Input
• Sending a strong message
  • Conditionally call conversion methods
  • Define your own conversion protocols
  • Define conversions to user-defined types
  • Use built-in conversion functions
  • Use the Array() conversion function to array-ify inputs
  • Define conversion functions
  • Replace “string typing” with classes
  • Wrap collaborators in Adapters
  • Use transparent adapters to gradually introduce abstraction
  • Reject unworkable values with preconditions
  • Use #fetch to assert the presence of Hash keys
  • Document assumptions with assertions
  • Handle special cases with a Guard Clause
  • Represent special cases as objects
  • Represent do-nothing cases as null objects
  • Substitute a benign value for =nil=
  • Use #fetch for defaults
  • Use symbols as placeholder objects
  • Bundle arguments into parameter objects
  • Yield a parameter builder object
  • Receive policies instead of data
• Delivering Output
  • Write total functions
  • Call back instead of returning
  • Represent failure with a benign value
  • Represent failure with a special case object
  • Return a status object
  • Yield a status object
  • Signal early termination with =throw=
• Handling Failure
  • Prefer top-level rescue clause
  • Use checked methods for risky operations
  • Use bouncer methods
• Refactoring for Confidence
• MetricFu
• Stringer
• Parting Words

And here’s a video of the talk that started it all:

http://www.youtube.com/watch?v=T8J0j2xJFgQ

And here’s that big friendly “buy now” button again!

UPDATE: This giveaway is now over. Thanks to everyone who entered, and congrats to the winners!

Everyone

Everyone who enters will receive a 20% discount for Cloudapp Pro and 10% discount on all AppSignal plans for the first 12 months! Yep, everyone!

Grand Prize

One lucky winner will receive:

• A full year of RubyTapas!
• Free ticket to Barcelona Ruby Conference (travel/accommodations not included)
• 1-year free AppSignal Small plan
• 1-year membership to learnable.com
• 1-year subscription to CloudApp Pro
• 1-year subscription to RailsCasts Pro
• 2-month subscription to thoughtbot Learn Prime
• Jump Start Sinatra by Darren Jones
• Rails As She Is Spoke by Giles Bowkett
• Upgrading to Rails 4 by Andy Lindeman
• Prosthetics And Orthotics: Lessons Learned In Building Plugins For Backbone.js by Derick Bailey
• Master Space and Time With JavaScript by Noel Rappin
• Clean Ruby by Jim Gay
• Rebuilding Rails by Noah Gibbs
• Ruby Under a Microscope by Pat Shaughnessy
• Everyday Rails Testing with RSpec by Aaron Sumner
• Working With Unix Processes by Jesse Storimer
• Mobile Web Patterns with Backbone.js by Nick Gauthier
• Gitty App for GitHub

Second Prize

Two winners will receive this package:

• Six months of RubyTapas!
• Free ticket to Barcelona Ruby Conference (travel/accommodations not included)
• 6-month free AppSignal Small plan
• 6-month subscription to CloudApp Pro
• 6-month subscription to RailsCasts Pro
• Jump Start Sinatra by Darren Jones
• Rails As She Is Spoke by Giles Bowkett
• Upgrading to Rails 4 by Andy Lindeman
• Prosthetics And Orthotics: Lessons Learned In Building Plugins For Backbone.js by Derick Bailey
• Master Space and Time With JavaScript by Noel Rappin
• Clean Ruby by Jim Gay
• Rebuilding Rails by Noah Gibbs
• Ruby Under a Microscope by Pat Shaughnessy
• Everyday Rails Testing with RSpec by Aaron Sumner
• Working With Unix Processes by Jesse Storimer
• Mobile Web Patterns with Backbone.js by Nick Gauthier
• Gitty App for GitHub

Third Prize

97 more winners will receive the following prizes:

• A 3-month Cloudapp Pro membership
• 1-month subscription to RailsCasts Pro
• 25% discount on all AppSignal plans for the first 12 months
• 10% off Upgrading to Rails 4 by Andy Lindeman
• A coupon to get Everyday Rails Testing with RSpec by Aaron Sumner for just $8
• 10% off Working With Unix Processes by Jesse Storimer
• 10% off Master Space and Time With JavaScript by Noel Rappin
• $5.00 off Prosthetics And Orthotics: Lessons Learned In Building Plugins For Backbone.js by Derick Bailey
• $10.00 off Mobile Web Patterns with Backbone.js by Nick Gauthier

How to enter

Just fill out the form below! All entries must be submitted by May 21st at 23:59 UTC. I’ll announce the winners on this blog on May 22nd.

“Consulting pair programmer” isn’t exactly a crowded niche. I know of some other freelance programmers who do a lot of remote pairing, but I’ve yet to hear of anyone else making a living on short (2-hour) sessions with many different clients. I wasn’t at all sure what the response would be like when I started the experiment. I half expected that I’d get an initial burst of interest which would then tail off after a month or two.

In actuality, the response has yet to abate. I’ve had little trouble filling my available time with pairing appointments, and I’m still receiving a steady stream of new inquiries every week. All this from no PR other than some links on my blog and an occasional mention on Twitter or Ruby Rogues.

It’s been a remarkable experience. Getting to see the Ruby world from the perspective of many different programmers with a broad range of experience has been incredibly valuable. Especially as someone who tries to put a lot of educational material out, I can’t think of a better way to get an idea of where people are coming from, and what concepts they have the most trouble with.

It has also been exhausting. As anyone who with pair-programming experience knows, a productive pairing session can leave you much more drained than the equivalent amount of time spent solo coding. Pairing keeps the focus and energy high. Not to mention that when people are paying for my time, I have a strong imperative to be 100% “on” from beginning to end. Some days I did four sessions—that’s four different people, working on four different projects—in a row. Those were exhilarating days, but also some of the most tiring I’ve known in my career.

In late September I launched RubyTapas, my subscription screencast service. Since then it has grown by leaps and bounds. As of today it has well over 1000 subscribers. This has caused a shift in my priorities. I’m no longer a consultant with some products on the side. RubyTapas is my primary source of income, and hence it is now my focus.

The months of transition, during which RubyTapas wasn’t yet big enough to support us, but still required a great deal of time in order to turn out three videos a week, were difficult. Keeping up with enough pairing sessions to pay the bills;  spending many hours writing, recording, and editing videos; and oh yeah, also dealing with a new baby with only a tenuous grasp on the concept of “sleep”… let’s just say I didn’t get a lot of rest. We talk about technical debt; I feel like I’ve run up some stress debt which it’s now time to pay down.

Which is why I’ve decided to put my pairing services on hiatus for a while. I’m going to focus on making videos, finishing Confident Ruby, and on my rather full 2013 conference schedule. I’ll obviously be keeping my scheduled appointments, and those of you on my OSS pairing queue: don’t worry, I’ll keep going down the list. But I’m taking down my pairing contact form for now.

There’s a lot I could write about my experiences pairing with so many different developers. I’m not really sure where to start though, so I’d like to open the floor instead. What would you like to know? As they say on Reddit: AMA!