Scraping the bottom of the "Developer Productivity" barrel

He cites a few self-run benchmarks. A couple are impressive: a certain build shaves off 2 minute and 14 seconds (a little under 50% faster), and running 1846 NUnit tests brings a 2 minute and 40 second process down to 37 seconds (about 80% faster). The rest… not so much. Most are cutting scant seconds off of already quick processes.

I do believe that there are some expenditures that are worth it. Developers spend 8 hours a day sitting, so buying them extremely comfortable chairs makes a huge difference. Similarly, developers spend 8 hours a day looking at their monitors, and buying them each two large monitors allows them to keep their work and minds better organized.

That means the Intel one costs almost 14 times as much. If I’m buying this for my developers, I want to make sure it’s cost-effective. Let’s say I pay my developers an average of $52.00 per hour (to make the numbers easy). That means, to justify the extra $520.00 I’m spending to get this SSD, it needs to save them 10 hours over the course of their time with me. That’s 268 of those builds mentioned earlier, or 293 of those sets of NUnit tests.

Is this an outrageous number? No. But it’s also not an obvious win, like buying a pair of large monitors or a comfortable chair. It’s scraping the bottle of the barrel, to say the least. Unless he’s got a super awesome chair, a couple 24-inch monitors, and all the other productivity staples, I’d say his money would be much better spent elsewhere.