While most of them are well done and funny in their way, they are not actually parodies of O'Reilly, they are parodies of developer attitudes using O'Reilly cover style (similar to meme generator images).
As an O'Reilly parody I would expect something like "Official paper version of an OSS manual you can download on the project page". The Stack Overflow cover is kind of like that.
Staying in that definition: My comment was that the "deliberate exaggeration" would be an exaggeration of the original, not of something else. For example, these meme generator images using movie pictures with Brad Pitt are also not parodies of Brad Pitt.
The very first thing I do when starting a new project is putting the logging infrastructure in place. In production you don't want to spam stderr with each and every event. But if some operation fails the best way to understand why, is having a precise log of what chain of operations lead to this error.
I remember the good old days over 10 years ago debugging PHP in such a way. When I moved into .Net I thought "wow I never need a print statement again with the awesome debug tools". But leaving the comfortable embrace of Microsoft and even today I'm using print / console.log().
The amount of questions I find on StackOverflow that could have been found with a simple Google search makes me think there really is a need to read effective Googling of error messages.
Often times stack overflow is the first google result for certain types of error messages, and the responses are generally useful for both fixing and understanding the problem.
The refrigerator is where you put the refrigerator magnets, right? At least until the acid kicks in.
http://i.imgur.com/dy0ii.png