Getting Real

“I have a book for you. It’s called Getting Real.”

That’s not exactly a phrase a woman would take well. If she’s irritated with you for telling her she can’t have what she wants, that’s doubly so. She definitely won’t think that you’re talking about a real book written by 37Signals.

When Jared gave me that exact phrase, I had to remove myself from the situation we were in, calm down, and deal with it later. I laughed when he brought me a book with the actual title of Getting Real. And here I thought he was just giving me shit.

First Impressions

Getting Real

The wisdom dispensed therein is simple. The presentation of their book fits nicely with the message that they’re trying to convey. No individual section is larger than three or four pages. The chunks are well spaced and each individual chunk has a clearly defined lesson to impart.

A Deeper Look

The one bad thing I have to say about the book is that the sections are too short. I’m the sort of individual who adores exhaustive detail. I want to not only know the how, but the why in as many ways as possible. There’s something reassuring about having all of the facts and descriptions metered out like a roadmap to the best software plan. If you’re looking for a roadmap, this is not the book for you.

If what you are seeking is a peak into 37Signal’s rabbit hole, you have your wish. This book, if lacking the detail I normally prefer, contains a host of valuable information. Keep it clean. Keep it simple. Keep it iterative. Figure out what you need to accomplish and get it done quickly. A great software no one can use because it’s still in the sketch process does no one any good. Your great idea, if left unfulfilled, is just that… an idea.

But Will I Buy It?

I may buy my own copy of this book, just to keep myself on course when the time comes for real programming. It’s important to keep your enthusiasm and drive. Thankfully, Getting Real provides not only the information, but the inspiration. Many of the concepts are ones I’ve had and have had to fight for.

It’s always good to hear someone (a largely successful someone) thinks the way that you do. Surrounded as I am with competent, intelligent people, this book may rest on the shelf for long years before I pick it up again. If you’re living it, you often don’t need reminding.

Ultimately, they wrote their book like they write their software. You’ll not only get the information in the book, but you’ll see it in play by the text on the page. These are the gents who brought us Ruby on Rails.

Should we expect anything else?