time change
You're at a stopping point in your code, casually defined as being able to verbally list the features without having to add more disclaimers than your audience has attention span for. Now it's time for the misc fixes, the finesse postponements, the other branches of functionality you always intended. But there's more: now that you see your product working in concert with your overall system (this can be technology or workflow), you know you need to prioritize to make that as efficient as possible. Your product has this additional kind of customer, which is the next thing in the assembly line to receive the results. In short, your old cut line in your feature list may no longer apply.
With losing the hour, combined with natural weekend drift in schedules (no way I get up at 5am on Sunday just to keep me used to it on Monday, for example), I'm looking at a real whammy of a thought problem. I've taken a step back and reasessed, and I have a new feature list broken out into tasks, with the critical path item labelled and dated. Now it's time to start: but dare I start on so little sleep?
It's perfectly working code, sortof. Now it's time to delete and replace with initially non-working but eventually more functional code, that exists in a different structure than the old. High frontal lobe stuff. It just seems unwise somehow...