3 ms·
The slow part is the death-knell. It's not just that it takes longer for you to complete your task, it's also that you get distracted while waiting for your slo
by piaw 16y ago
The slow part is the death-knell. It's not just that it takes longer for you to complete your task, it's also that you get distracted while waiting for your slow machine. What's your first response if you hit the compile key and it takes longer than a few seconds? You flip over to browsing the web. That interrupted flow cost you way more than $5000. If you could spend $5000 to make that go away for every engineer in the company, the increased productivity will more than pay for itself over time.
Sometimes, that means more than just paying for the machine on the engineer's desk, it could mean spending money on a cluster of machines just to do distributed compiles. That's also money well spent. Basically, any time you can keep an engineer from interrupting flow by spending money, it's a decision worth careful consideration.
As an extreme example, Google spent millions on SSDs for its source control systems to speed up submits. Money well spent.
- vijaydev 16y agoflipping over to browse the web the moment you have a couple of minutes free is probably why some companies block access. Employers expect their employees to focus on their job and not flip over at every chance. But what the blocking means for us is something that they ll never understand..
- piaw 16y agoWhat do you expect engineers to do while code compiles? And flipping to a browser could also mean checking e-mail, filling out expense reports, or scheduling a design meeting. The problem is: even if those things are a productive use of an employee's time, they still interrupt your flow.
- vijaydev 16y agoI think you got me wrong. I'm one of those engineers who flip over :) What I meant was that the employers do not understand this behavior and all they could do to prevent this is to block access to the Internet which actually harms our work more.