A 'deadlock' on the block..
Posted: Sat May 24, 2008 8:17 pm
Coding if fun, its even more fun in newlisp, well we all know that.
Now last 3 days I did some coding, intense coding, monitoring actually.
With a very tight deadline. Now coding is fun but when you run into
a 'deadlock' situation its starting to get serious. Why? because you
first dont see the 'deadlock'. You start working around problems and
try to fix on after the other. Still its not working 100%. You start thinking
of seeking a different job. No option!. Can I do this? Whats wrong with
the code? Then you find some tweaked OS settings then some other
tiny settings.You try again. Still no result. Still no idea the problem is
a 'deadlock'. What do i do wrong. Rereading the manual. No its not the
language I use. Testing testing and testing.. always a tiny new problem.
At that stage youre too deep into the code and forget the MAIN problem/
target you where working on. Relaxing Relaxing, concentrate. reviewing
the code. rethinking the problem. stripping all extra's that where added.
Ending up at where it all started, the basics. Then you see it. A blink of
mind refreshment, its a 'deadlock'. Something that cant be fixed without
human interaction. So here I am now..and fully loaded with code in a mind
that blows sideways but a solution that works, 'press the red button!'
How strange it is in programming to lose the clear-view and main
design of the program. Relax! the magic word..
;-)
Now last 3 days I did some coding, intense coding, monitoring actually.
With a very tight deadline. Now coding is fun but when you run into
a 'deadlock' situation its starting to get serious. Why? because you
first dont see the 'deadlock'. You start working around problems and
try to fix on after the other. Still its not working 100%. You start thinking
of seeking a different job. No option!. Can I do this? Whats wrong with
the code? Then you find some tweaked OS settings then some other
tiny settings.You try again. Still no result. Still no idea the problem is
a 'deadlock'. What do i do wrong. Rereading the manual. No its not the
language I use. Testing testing and testing.. always a tiny new problem.
At that stage youre too deep into the code and forget the MAIN problem/
target you where working on. Relaxing Relaxing, concentrate. reviewing
the code. rethinking the problem. stripping all extra's that where added.
Ending up at where it all started, the basics. Then you see it. A blink of
mind refreshment, its a 'deadlock'. Something that cant be fixed without
human interaction. So here I am now..and fully loaded with code in a mind
that blows sideways but a solution that works, 'press the red button!'
How strange it is in programming to lose the clear-view and main
design of the program. Relax! the magic word..
;-)