Software is (often) written by humans

As i mentioned yesterday i am currently reading the book "Java - Concurrency in practice".
Well, i am just on page 100 so this blog whill not review the book yet.
But i just encountered a small section that is about reasoning of concurrency practice in 3rd party code. The author nicely calls for better documentation (of cause, we all do a lot!..) of the implemented policy (implicit locking, GuardedBy annotations, overall strategy and threadsafety at all). If there is no such documentation we have to reason about it.
But in my opion this just the best approach of you are on an academia trip (which is not bad).
There is a much more relieable, efficient and economic approach: ask humans!
Even the "worst & most commercial" oriented companies are building communities and often invest into open source environments (not neccessarily open source code but the comminity intention behind it): so if you start guessing things try to digest your thoughts so long and put it on (the correct) mailinglist or newsgroup.
What are the benefits?
well,

1. people with similar guessing find it on google
2. people with wrong guessing find the correct answer on google (more important perhaps)
3. the authors get the point and could pin it to their upcoming releases (better docs)
4. you do something good to the world
   

Just a word about the passed chapters i already read: very,very,very recommendable book! I am going to reject all osgi-bundles authored by people not reading this book (or having a reasonable past about concurrency). Damn.. thats so currious.
More on concurrency later!