Ya.  It's about coding, so you can move on now you pervs.

Do you still get a thrill when your current project comes together and produces the results you wanted?

Or, are you so far advanced that you only get aroused (heh) when something <>doesn't work?

im probably more towards the later. I used to think it was cool when i could accomplish something. now i kind of think its cool when i can't, at least in my language of choice. then to figure it out.

thats partly why I tend to take on projects of fixing other peoples code. its more of a challenge than just grinding out the solution. I used to be interested in my projects until about the 90-95% point. now, im interested to about the 5% mark... LOL its gotten really bad since midway through my last employment, and now im damaged forever. I like the planning and architecture and design

asp

 ects, but man, the code is just a grind now.

I get the thrill when my users go "This is so easy!" Means I did the architecture part right.
I live for the dream, endure the code, and get satisfied when it goes into production.

I'm still excited by the code, sometimes at the expense of the actual project ;-)

Cheers,
td

'hello world' excites me.

the kaptain enjoys the idea and planning phases but having to actually code the systems are a pain.  the exception being when the idea presents a challenge (or perceived challenge) as far as coding goes but once the challenge has been beaten the rest is just a pain

the Kaptain will get excited sometimes with new languages and figuring out how to do things in them that he takes for granted in ones he is already good at.