in reply to
How do you code?
Yeah, I know it..
Let's say I've got no problem to code 7 days the week, sleeping from 4AM to 10AM and sitting on front of the screen the rest of the day/night.
I've also made the experience I get really productive after one or two 16 hour days without a break.
I only need self-discipline to eat and drink enough in such times.
However, I try to do things besides hacking, therefore usually I'm hacking perhaps one or two months a year in such a manner.
The rest of the time I do force myself to spend time with my hobbies like climbing, my studies in philosophy, making some music, painting, ...
Therefore I normally sit around 2 hours a day at the pc.
If I do some work for a customer, because I need the money (I'm self-employed), I've got a great excuse to spend the whole day in front of the screen again.
I always hadve ideas in my mind about new projects, and there are around 5 on the stack I'm working on.
And yes, there's a difference to me between hacking for fun and doing some work fo a customer:
If I do program for fun, I can do whatever I want - there's no pressure, and I can, e.g., if need a threaded server, play around with threads in perl some days and look for the optimized solution.
On the other hand, if I have to write a threaded server for my work, I have to force myself to look for the shortest solution (instead of having an optimized and elegant solution, having the solution done as fast as possible), what I don't like.
Programming is a kind of art and expression to me - so possibly I'll never get completely professional, I just love hacking too much - Just playing around with an aspect of a project for some days instead of just getting it done in some hours...