I often find the key to fast development is having key insights into the problem, picking simple solutions, and avoiding programming down the wrong path. All those things require being fresh. I'm positive that I'm more productive in 6 hour blocks than 12 hour blocks.
The problem is that managers take the "Building Software" metaphor literally. If we were laying bricks, sure, we could get more done in 15 hours than 8. But we're not, we're trying to solve problems. Tired, stressed programmers make bad decisions and those bad decisions take longer to code. (Not to mention test and debug).
My question to a friend in the financial sector was if stock analysts have enough information to spot troubled companies like Worldcom. He said that the analyst he sits next to has been yelling since last november to get out of Worldcom stock. The biggest red flag apparently was the huge loans to the CEO. When you are looking to buy stock wouldn't it be nice to see a ranking of how many warning signs exist in the company?
I often find the key to fast development is having key insights into the problem, picking simple solutions, and avoiding programming down the wrong path. All those things require being fresh. I'm positive that I'm more productive in 6 hour blocks than 12 hour blocks.
The problem is that managers take the "Building Software" metaphor literally. If we were laying bricks, sure, we could get more done in 15 hours than 8. But we're not, we're trying to solve problems. Tired, stressed programmers make bad decisions and those bad decisions take longer to code. (Not to mention test and debug).
My question to a friend in the financial sector was if stock analysts have enough information to spot troubled companies like Worldcom. He said that the analyst he sits next to has been yelling since last november to get out of Worldcom stock. The biggest red flag apparently was the huge loans to the CEO. When you are looking to buy stock wouldn't it be nice to see a ranking of how many warning signs exist in the company?