The best programmer I know in person agonizes over his approaches until it satisfies his high level of standard. He is a professional, not an amateur who does his work for fun. Does he have fun when he works? Yes, sometimes, but not all the time.
The best programmer I know in person agonizes over his approaches until it satisfies his high level of standard. He is a professional, not an amateur who does his work for fun. Does he have fun when he works? Yes, sometimes, but not all the time.
Lowe by the way was a fascinating character who, in addition to being one of the worlds top athletes, studied mathematics and would reportedly bring math text books on expeditions to keep himself entertained.
This is particularly true when we're talking about a subject that's notoriously tricky to measure (programmer productivity) and subjective (what the hell makes for a good programmer anyway?).
At the end of the day, there's only so much usable data to work with, and you can't blame people for making decisions on limited data. That said, if you know of any data that disproves his point, I'd love to see it.