Thank you, David Demaree, for this blog …
Since the first of the year I’ve been trying to write one of that sort of post where the blogger describes the tools they use. Obviously, I haven’t succeeded yet. And what’s more, it’s taken me until now to precisely identify why it’s been so hard.
It’s not that I find these “setup” posts to be a form of pornography. They are, and I do, but in this scenario I would be the porn star, which (when you look at it that way) doesn’t seem that bad. And it’s not that my setup isn’t interesting. It’s not that mind-blowing or innovative, honestly, but over the years I’ve learned a lot about what I need to do my job and that knowledge feels worth sharing.
What I’ve concluded, rather, is that in trying to talk about my tools in a single post, I was going about it totally the wrong way. Tools and best practices are things I care deeply about, and trying to cram everything into a single, 5,000-word monster post would be exhausting for me to write, at least as tiresome for you to read, and would still do no justice to the subject.
So I’ve decided to write about my tools in a series of posts, starting with this one about my Ruby environment on OS X. Future posts in this series will cover other aspects of my day-to-day workflow, such as how I use Git, how I’ve configured Apache and Pow to work together as a team, and a whole post on what text editor I use.
For now, let’s talk about Ruby. In addition to describing my personal Ruby setup, I’ll also explain how to get it up and running on a new Mac. This is as good at time as any to mention that I use only Apple computers running the latest public/stable release of OS X (currently “Lion”, version 10.7.3). A future post in this series may explain a bit about my hardware choices, or how I’ve configured my Mac system for maximum awesomeness, but to be clear: while what follows is largely in tutorial format, the information here is only intended to be relevant on OS X.