From this site: http://news.bbc.co.uk/1/hi/magazine/4545714.stm
Prof Alan Hedge, Cornell University, found typing accuracy depends on room temperature:
At 77ºF employees had a 10% error rate
At 68ºF speed slowed by almost half, and error rate rose to 25%
Hedge also estimated this caused a 10% increase in labour costs per worker hour
Wouldn't mind those temps being converted to Celcius. But for sure when I'm code my hands really suffer and my typing and gameplay becomes poor. Also I play the guitar and cold hands are simply awful.
Actually the main point of the article is this
Which kind of backs up my theory that you should always strive for accuracy and double check your work as what makes a small mistake large is purely down to context. For example Copy/Paste errors are fairly common in code, e.g. you copy/paste a section of code and change some of it but forget to change another critical part. It all appears fine until your biggest client runs it and calls the Helpdesk with "our entire system" has gone done type thing. Actaully if you are having to copy/paste code, you should probably make a resuseable function and of course you should test, test and test again. It always the last test of 50 that shows up a bug in my experience ;-)
Prof Alan Hedge, Cornell University, found typing accuracy depends on room temperature:
At 77ºF employees had a 10% error rate
At 68ºF speed slowed by almost half, and error rate rose to 25%
Hedge also estimated this caused a 10% increase in labour costs per worker hour
Wouldn't mind those temps being converted to Celcius. But for sure when I'm code my hands really suffer and my typing and gameplay becomes poor. Also I play the guitar and cold hands are simply awful.
Actually the main point of the article is this
"It happens millions of times a day, but once in a while the result can be devastating. Earlier this month a trader on the Tokyo stock market accidentally blew £190m because of a simple typing error.
A computer which should have cancelled the transaction failed to click in, and this further embarrassment led to the resignation on Tuesday of the head of the Tokyo stock exchange."
A computer which should have cancelled the transaction failed to click in, and this further embarrassment led to the resignation on Tuesday of the head of the Tokyo stock exchange."
Which kind of backs up my theory that you should always strive for accuracy and double check your work as what makes a small mistake large is purely down to context. For example Copy/Paste errors are fairly common in code, e.g. you copy/paste a section of code and change some of it but forget to change another critical part. It all appears fine until your biggest client runs it and calls the Helpdesk with "our entire system" has gone done type thing. Actaully if you are having to copy/paste code, you should probably make a resuseable function and of course you should test, test and test again. It always the last test of 50 that shows up a bug in my experience ;-)