> I was looking at some slides from a presentation about testing and 
> developer productivity. One slide was a photograph of an actual whiteboard 
> at Google HQ, listing the things that had reduced productivity on a 
> particular day:

Sounds an interesting task, I should suggest people here do that.  But one 
of the problems here I see is that a lot of people count the "unproductive" 
work as productive.  For example if they spend a day trying to fix a problem 
with an incorrectly designed thing, they count that as a good productive 
day's work.  They don't realise their job is to design things correctly, and 
not to design things incorrectly and then fix them.

Post a reply to this message