How to work with permanent, burning fatigue?
Posted: Thu Jan 10, 2008 5:31 am
There's a moment in which, after months or even years of having to implement/reimplement and improve a project, one feels that everything about it becomes tedious.
It isn't loss of interest, ideas, creativity, even one knows what to do most of the time.
But when it's time to start working, creating a new source file or documentation file, one starts mentally rambling about what will put there, as a sort of automatic fatigue starts loading until in a few seconds one not even gets to create the new file, much less putting things in it.
And if ever one manages to advance, it will be a very painful proces, will span several hours only to edit some bit and then we will give up for several hours to come.
Has anyone faced it? Does somebody knows how to avoid it, or at least minimize it to the point where having to almost rewrite a full big project without anyone else's help doesn't become nearly impossible after N times of repeating such stuff?
It isn't loss of interest, ideas, creativity, even one knows what to do most of the time.
But when it's time to start working, creating a new source file or documentation file, one starts mentally rambling about what will put there, as a sort of automatic fatigue starts loading until in a few seconds one not even gets to create the new file, much less putting things in it.
And if ever one manages to advance, it will be a very painful proces, will span several hours only to edit some bit and then we will give up for several hours to come.
Has anyone faced it? Does somebody knows how to avoid it, or at least minimize it to the point where having to almost rewrite a full big project without anyone else's help doesn't become nearly impossible after N times of repeating such stuff?