tea and coding

Okay, so I should be writing some nifty code that does something. What I'm doing instead is trying to think of what else I could possibly do. There is the T. Prachett book that I started. I have a tendency to read those in 24 hours or less and I'm trying to make this one last a little bit longer. I also could play civilization, but I don't know if having my eyeballs fall out at about 1:30am would be in my best interest.

It's not that I don't like writing code, but I have this problem with attention span. The really interesting problems are usually surrounded by considerable time spent doing boring stuff. It's kind of fun to twist your mind inside a data structure the size of the ritz. But it's no fun to have to write all the boring code around it that actually makes it accessible to humans who really don't understand or give a shit about what a piece of work it is. So I code "look and feel" for hours so that someone who thinks a hash is something you smoke can say ..

"I don't like it".

"Which part didn't you like? Is there some part in particular that's clunky, hard to work with, we'll get that fixed right up. When was the last time you looked at it?"

"Umm... what did you say the address to the demo site was again?"

I tell them.

"Well.... What was my login?"

*clickity, clickity, click* Check last login date for client's user. *Null* Ah, so that would be never.