I tend to cycle through different patterns, often depending on workload, season changes, etc. I'm currently up pretty much all night and sleeping in until noon

I tend to cycle through different patterns, often depending on workload, season changes, etc. I'm currently up pretty much all night and sleeping in until noonish, and since I set my own hours I often just get done communication stuff during the day then work on programming at night, with some socializing in between :) It can be challenging though, since staying up late can create a tendency to overwork, and often in a fairly unproductive way. I try to keep semi-balanced with a less-is-more approach. You don't need or want to code 12 hours a day. If I can do 6 hours I've had a really good day. If I get at least one good bit of work done, even if it took an hour to do, I'm happy with that. And that seems to be a realistic pace compared to other programmers anyway, in my experience at least. Not to say others are slow, I just mean that throwing more hours at a problem is often a lot like throwing more programmers on a project: there's a decrease in efficiency with each one added.