News for hackers. Stuff that matters.

A comment on Coding Horror: Pressing the Software Turbo Button. Parent comment

Re:Coding Horror: Pressing the Software Turbo Button by swilliams on Tuesday December 23, 2008 @11:25AM (#407704)
No. A slow machine is just aggravating. If I have to wait very long for a compile, the IDE, anything, there's a good chance I am going to get distracted and do something else. I'll typically have tons of things open at once, already slowing things down a bit; having old hardware is just too much on top.

It is important to check for performance on slow machines, but that can be done on a virtual machine.

[ Parent | on HN ]
Re:Coding Horror: Pressing the Software Turbo Button by light3 on Tuesday December 23, 2008 @11:31PM (#408507)
Seconded, its extremely aggravating, I remember clearly when I had the horror of working with an old version of .NET C# with a big project on a SHARED slow server, which took roughly 1-2mins to compile, can you imagine trying to learn and debug C# code under this environment? Right, not a good idea.
[ Parent | on HN ]
Re:Coding Horror: Pressing the Software Turbo Button by dcminter on Tuesday December 23, 2008 @11:55PM (#408526)
Sure, it's annoying. But I didn't say it was nice, I said it was a good incentive for the developer to create software that was snappy.

Those suggesting the use of a separate slow test environment are, I submit, being unrealistic about real-world practices in testing.

[ Parent | on HN ]