So the video was posted previously, but I think new info has surfaced here such as that 3 Googlers tried to infiltrate the JrVip sections.
Basically the part of Google that would benefit from reading BHW, would be the part that dedupes content after it's stored in Big Table gzipped from googlebot. Once it hits the Map/Reduce phase that separates it by key/value pairs, it's too late.
So what the deduping process entails is matching content against a library of duplicate content hashes, or regular expressions that detect black-hattery. Generally whitespace is ignored, line endings, ect... Googlebot does process Javascript and AJAX, as well as flash, so these are no longer good ways to hide code from Google. Even outputting different content depending on googlebot being in the User-Agent doesn't really work too well because Google has the man power to check manually.
The info that could really hurt other BHW posters is when people post code snippets or HTML or DOM snippets, since Googlers can copy/paste those into it's dedupe library. Merely explaining how something works, can't really hurt a method, because without the implementation, Google is clueless on what regex to implement on it's side to stop it.
So just a heads up, if you have some method that really does make you money with Google, only post the concept and not any actual code or script. If you resell it as a service or as software, Google, or whatever start-up it's targeting will probably wind up getting it and using it to reverse engineer a block. Note that they probably will not pay for it in the process.