3 ms·
Actually, that's how I interpreted it, but I appreciate the clarification. But I still disagree. Anecdotally, I've found that coding for 6 hours a days gets m
by sanj 19y ago
Actually, that's how I interpreted it, but I appreciate the clarification.
But I still disagree. Anecdotally, I've found that coding for 6 hours a days gets more features implemented and bugs fixed than coding for 14 hours a day.
The loss of mental acuity, clarity and creativity (again, this is for me, and anecdotal) is simply too high a price to pay.
- pg 19y agoAnecdotally, I've found that coding for 6 hours a days gets more features implemented and bugs fixed than coding for 14 hours a day. Sure, in the long term. But when you have a big demo or a customer deadline coming up in 2 days, or a server crashing right now, it often pays to keep working past 6 hours.
- sanj 19y agoThen the injury analogy still holds. I hold up the Schilling's bloody sock as Exhibit A: http://nbcsports.msnbc.com/id/6948862/ http://nbcsports.msnbc.com/id/6948862/
- maw 19y agoCurt Schilling probably would have had problems in subsequent years had he pitched in the playoffs in 2004 or not.