This is an excellent analogy! I will steal it! :>
Yes -- so long as you're not buying one just to keep up with the guy down the street!
Almost everything that I use a computer for is "meatware limited". A faster computer, newer OS, etc. just means the machine waits for me, more (relatively speaking).
When I got started in this business, if you were LUCKY, you could do TWO iterations of the edit-build-test cycle in an 8 hour shift. The tools were SO slow and the technology so inflexible, that you spent a lot of time waiting for the tools *or* performing "acts of contrition" to appease the silicon gods and coerce them to honor your prayers.
So, you learned how to better "schedule" your efforts. Anticipate the next problem when solving the current one. I.e., don't just install the "fix" for the current problem but also install any stubs, etc. to let you get a headstart understanding/verifying the behavior of the NEXT thing you'll be testing.
Instead of: [fix first problem, build new system, test] "Great, that works!" [create test conditions for next step, build new system] "Hmmm, that's a problem..." [fix second problem, build new system, test] "Great, that works!" do: [fix first problem, create test conditions for next step, build, test] "Great, that works! But, there's a problem with..." [fix second problem, create test conditions for next step, build, test] "OK, that's fixed! Now there's a problem with..."
If you keep this sort of mindset, you're always a step ahead of the guy who relies on a faster machine to just keep "throwing darts" at his perceived problems: "Hmmm... that didn't work, let's TRY this..." And, less needing of the latest and greatest (speed, etc.)
"Go do something else while you're waiting for the machine" instead of: "Buy a faster machine so you're not waiting as much"