Coding at night is often better for building large pieces of code because there's no interruption. Where I work you can watch the SVN commit messages in the de

Coding at night is often better for building large pieces of code because there's no interruption. Where I work you can watch the SVN commit messages in the dev channel coming by until about 5:00 AM several times a week. I'm on the dev team and do this myself about every other week. This doesn't mean we're a bad company whipping every last bit of productivity out of people. It just means that sometimes you're on a roll, you're in the zone and you have to keep going. We get that. It's fine. Just don't show up at the office the next day. Talented developers often are slightly anarchic, neurotic and just a wee bit obsessive. Even the most straight-laced "I only work 9-to-5" developers sometimes make a 4:00 AM commit because "I couldn't sleep and just figured out how we could re-use the token substitution in the webservices interface variables by mapping them to the corresponding domain entity attributes and applying the usual validation rules to them!" Yeah, we're a model of sanity where I work :) Generally speaking, as a developer you can start work between 8:00 and 12:00, but if you're just starting here the start time is 8:00 to 10:00 because you need supervision, education and time in pair-programming.