I've been working on my N.A.N.Y. 2010 app since August. It's going quite well, and is, by my estimation, about 90% "done". Some of my RPG players have done some testing for me. I still have some finishing-up touches to make. Perhaps a few more hours of coding. What I've been finding is that I've begun to lose a little "steam", or drive, to work on it.
I've noticed a similar pattern over the past four or five years when working on a fairly sizable project: I start off great guns, working lots of hours per week with great enthusiasm. As time goes on, a sense of ennui gradually steals over me.
Don't get me wrong: I fully intend to finish the project, and it will be useful when completed -- albeit to a rather limited audience.
I wonder if the rest of you coders experience a similar ennui-phenomenon?
I've noticed a similar pattern over the past four or five years when working on a fairly sizable project: I start off great guns, working lots of hours per week with great enthusiasm. As time goes on, a sense of ennui gradually steals over me.
Don't get me wrong: I fully intend to finish the project, and it will be useful when completed -- albeit to a rather limited audience.
I wonder if the rest of you coders experience a similar ennui-phenomenon?





















. The last decade I was in corporate America, the hardest part of anything I did, whether report, Web site, program, whatever, was the last 5%-10%. Seemed as though every time the end of the tunnel - not the light at the end of the tunnel, but the end of the tunnel - showed up, I'd slow down. Hardest work I did was that last 5%-10%. Oh, I'd finish ... but it hurt
.
.
- carpe noctem

... but to trust my memory and go to sleep satisfied




