in reply to Re^2: The problem of documenting complex modules.(Summation.)
in thread The problem of documenting complex modules.

I skip the documentation and I look for "examples/" and "t/"ests as its code that actually supposed to run :)

I'd have to need what that module did very, very badly before I'd try to piece together how to use its functionality from a few dozen or hundred ok()/nok() tests.

Reminds me of another module I recently looked at:

This is how they want to encourage me to use their code? Could they have made working out what it is and how to use it more obscure? Perhaps they could have encrypted it all and posted a web treasure hunt to track down the decryption keys al la GCHQ."Starting from entrants must hunt down four codes hidden around the world-wide web."

I should coco. I don't care if it is free code, my time is more valuable than that.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!