Koda

If there was one book I would recommend to someone interested in learning a programming language, why ’s (poignant) guide to Ruby would be it. Why’s seemingly infinite creativity and excellent writing make this book a treat to read, and the beautifully clean layout and why’s comic art are icing on the cake.

When I first discovered it two days ago, I knew immediately that why ’s (poignant) guide to Ruby was unlike any programming literature I’d read before. In fact, the book takes every opportunity available to poke fun at books I had previously read on the subject.

Admittedly - there is very little that this book does not take the opportunity to poke fun at - and in doing so, keeps what can be an unnecessarily dry topic truly entertaining and funny. You can tell a good programming book by it’s examples - and why has an endless supply of them. Thoughout the book you’ll encounter the esteemed teddy_bear_fee, chunky bacon, and so much many more.

One thing you’ll notice right away about why’s writing style is his eclectic and meandering approach to describing concepts. I’m sure this is a something most will either love or hate - and I think it’s a great idea. Through the sidebar topics and (at times lengthy) discourse, why introduces a whole spread of the philosophies surrounding open source, free content, his political/social opinions, you name it. I’m pretty sure it’ll come down to whether you agree with him or not, but I think that by covering these aspects to coding, why makes the (poignant) guide more than just a programming manual, but a peek into the eyes and culture of a representative of a programming community.

One thing I especially liked about what I’ve read is why’s emphasis on learning the language as a language, learning to speak it naturally instead of simply memorizing the rules. When it comes down to it, programming languages are not unlike any others: you have to learn to express yourself with them. Why’s (poignant) guide shows you how to do just that - poignantly.

From the book:

My conscience won’t let me call Ruby a computer language. That would imply that the language works primarily on the computer’s terms. That the language is designed to accommodate the computer, first and foremost. That therefore, we, the coders, are foreigners, seeking citizenship in the computer’s locale. It’s the computer’s language and we are translators for the world.

But what do you call the language when your brain begins to think in that language? When you start to use the language’s own words and colloquialisms to express yourself—Say, the computer can’t do that. How can it be the computer’s language? It is ours, we speak it natively!

We can no longer truthfully call it a computer language. It is coderspeak. It is the language of our thoughts.

Best. Programming Book. Ever.

I have to admit that I’ve always been a Python guy - but this book has really got me looking forward to learning Ruby.