Documentation Hell

Have a need to fix someone's problem.
Want to see it through feel the call.
A programmer/engineer cannot let it go.
What is broken must be fixed.
What is undone must be done, to death.

Working hard to put it down in lines and loops.
Make it build and watch it run.
Tweak, twiddle, paint and polish.
Test and test and test again.
Someone admits the damn thing is done.

Programing is an art and a science.
No code is ever done.
Something needs fixing, always, forever.
Only when the need is gone is it done.
But code jockeys must move on.

When coders can code no more.
When the binaries do what they are supposed to do.
When there is no excuse left to fiddle.
When all else has failed to fail.
It is time for to turn to the Doc Side.

Asking a code monkey to write docs.
Is a bit like asking a dog to climb a rope.
When it is done, you end up with a dog up a rope.
The next time you look at docs for software.
Remember just how useful that dog is up there.