5 ms·
Listen to the Stack Overflow podcast. The developer estimated that it would take "a few weeks". A day and a half of Joel's time sees like a fair trade to do t
by pkaler 18y ago
Listen to the Stack Overflow podcast. The developer estimated that it would take "a few weeks". A day and a half of Joel's time sees like a fair trade to do this experiment.
Listen to the podcast. The conversation starts at about 16:00 mark if that helps. I am seeing a ton of comments that don't understand the context of the article.
http://blog.stackoverflow.com/2009/03/podcast-47/ http://blog.stackoverflow.com/2009/03/podcast-47/
- jrockway 18y agoBut the developer wasn't going to take this brain-dead approach; he was going to do something that would actually help. Joel spent time and got nothing; the developer wanted to spend time doing something that would probably speed up the build.
- blahblahblah 18y agoExcept that he didn't "get nothing" out of the exercise. As he expected it would, the new drive did provide significant speedups for a variety of tasks and will undoubtedly improve his productivity enough to have been worth the time and money he spent on it. As it happens, it didn't improve the build speed specifically, but so what?
- icefox 18y agoYah, but I spent 10 minutes and read the ars article on the drives and got what took him several days to learn.
- sfg 18y agoHe got: snappier computers for everyone and a story to write about (key to his marketing).