Why Pivots don't do their best work at night

There is an interesting article by Swizec Teller over at Business Insider talking about why programmers do their best work late at night. This is not the case at Pivotal. Generally when we have clients committing code late at night, the team ends up having to refactor it and get tests around it the next day. Often leading to a net loss of productivity even if the amount of time invested was greater. So why then do so many developers seem to agree with the article? The article has two general theories, and unfortunately I think they are correct for most developers. However, rather than having developers commit all their code at night, Pivotal has better solutions to problems the article talks about. The first theory is that developers need to hold the whole code base in their head, and any interruptions will force them to start over. So late at night is the only time develo...