I've written code drunk (read: one beer, I'm a lightweight) a few times--mostly for personal projects, but at work occasionally. The results tend to vary: somet

I've written code drunk (read: one beer, I'm a lightweight) a few times--mostly for personal projects, but at work occasionally. The results tend to vary: sometimes it's bloody inspired, other times I have no idea what I was thinking. It does seem to help with ``analysis paralysis''; where there are so many conditions and overlapping cases to consider that you can't even begin writing the code. Sometimes forging blindly ahead helps you think through the problem better. But always check your commit logs the next day. :)