Choosing the Right Tool20 June 2012
Kyle Mestery of Cisco recently shared a link on Twitter about Marco Arment’s choice to move back to a dual Mac setup. The article started me thinking along two parallel lines:
First, it got me to thinking about my own Mac setup.
Second, I wondered if there was a similar parallel about the choice of tools in data centers today.
Allow me to explain. In his article, Marco talks about how he abandoned his dual Mac setup—in which he was using a 13” MacBook Air and a Mac Pro—for a single Mac setup using a really beefed up 15” MacBook Pro. He had hoped to reduce the overhead of managing multiple Macs by consolidating to a single Mac that would bring together the best attributes of both. What he found a year later was that his attempt to use one tool (the 15” MacBook Pro) really ended up being less beneficial instead of more beneficial. Instead of getting the best of both worlds, he instead inherited the drawbacks of both. To that end, he’s now moving back to a dual Mac setup.
<aside>Just as a point of clarification for those who might be unfamiliar with Apple’s product lines: the MacBook Air is a highly portable ultraslim notebook with limited expandability; the MacBook Pro is Apple’s more expandable and more powerful notebook; and the Mac Pro is a workstation-class desktop computer with oodles of CPU cores and gobs of RAM.</aside>
The first thought process that occurred to me regarded my own Mac setup. I recently purchased a Mac Pro because I needed a computer that could provide more raw compute capacity than my laptop possessed. Reading Marco’s article validated (in a way) my thinking. However, it also challenged me to consider the type and configuration of laptop that I use. I migrated from a 15” MacBook Pro to a smaller 13” MacBook Pro last year, but I still insisted on a MacBook Pro with 8GB of RAM instead of a lightweight MacBook Air with only 4GB of RAM. Don’t get me wrong; I’m extremely happy with my MBP. It does lead me to believe, though, that my next laptop choice needs to be a choice that optimizes its role. What do I mean by that? I chose a Mac Pro because I needed CPU power and lots of RAM. The Mac Pro was the right tool for that job. Similarly, when I select my next laptop, I need to prioritize what I need out of a laptop (weight, size, mobility) and choose the right tool for the job. Instead of choosing a laptop based on how expandable it is, perhaps I should be looking at how suited it is for a highly mobile worker.
There’s a second train of thought here as well, and this train of thought pertains to the tools that we, as IT professionals, choose for our data centers. We also need to make sure that we are selecting the right tool for the job. Marco’s experience shows that using a single tool to perform multiple functions doesn’t always work as well as one might think. He made his initial decision in an effort to reduce complexity—an admirable goal, I’d say. I believe that many IT professionals also strive to reduce complexity in their data centers, and many IT professionals probably do that by reducing the number of technologies, products, or vendors in their data center. But are we sacrificing the functionality of our data centers as a result? When we are choosing on the basis of reducing complexity instead of choosing the right tool for the job, what are we losing? What are we giving up? Instead of trying to shoehorn a solution we already have into a role for which it really isn’t suited simply to “reduce complexity,” shouldn’t we focus instead on choosing the right tool for the job? Shouldn’t we select tools that are optimized to perform the function we need them to perform? Yes, we do need standards and guidelines, and I’m not saying that we shouldn’t strive to keep complexity from overwhelming the data center. But what should be our primary driver for tool selection—the reduction of complexity via the re-use of a less-than-optimal tool, or the selection of a tool optimized for the function it needs to perform?
I’d love to hear your thoughts in the comments.Tags: General · Macintosh Previous Post: Technology Short Take #23 Next Post: Mid-Year Project Update