Wiriting documentation is the single most boring thing I can imagine.

Fuck, it'd be more entertaining watching paint dry, or seeing the grass grow.

True story

Not just paint or grass, there are flowers, trees, animals...
You can find all online at an accelerated pace son you can return to writing docs soon 😉

I actually see it as some sort of reflection of what I have done.
Usually I then find some big flaws in the way I did it and can actually correct it or do it better next time.

Like this I'm writing documentation more for myself, which most of the time means I'm the only one who understands it. But hey no one's complaining since no one reads it anyways.

@crapped Couldn't possibly agree more, unfortunately unit testing and documentation often go hand in hand.

There you go http://www.watching-grass-grow.com

Automatization is your friend. I was working with selenium the other day (complete bozo at it) and i figure out how to generate clean pdfs with testing results (even with screenshoots). Now plug that thing into your pipeline and enjoy that cappuccino