Working with Speed

When you do something too fast or too quick, you will tend to make many mistakes. In the end, you will need to fix it, hence the amount of time you actually spent are about the same as when you do something more carefully (slowly). [Slow here does not mean as slow as the snail or a turtle okay.]

Speed Kills
Speed Kills - Yes and No. You might want to speed up a little when you're on a highway (I hate slow drivers, especially woman.. sorry) or in terms of efficiency like (computer) system respond time or even waiting for your food in a restaurant. However, when you're writing a paperwork, or doing routine security checking (logs, etc..) on a server or applications, writing codes (computer program) , debugging (codes), speed only makes you vulnerable to mistakes, hence wasted even more of your valuable time.

There are some task or work that need more attention, hence more time. However there are also task or work that need very little time. Operational work that need less work from your brain (thinking) should not take too much of a time to do as compare to a work that need more attention hence more work from your brain.

Bank teller handling operational counter job didn't even need to look at the number on the keyboard, and they handle customer request very fast. However a technical support executive will need more time trying to find a solution why is his application on the UNIX server stop responding every now and then - it's easier to just kill and run the script, but that won't solve the actual underlying problem. So you just keep on coming back on the problem again and again - hence wasting very large amount of time attending an old dying UNIX server.