Re:Parody O'Reilly book covers
by elcapitan on Saturday April 09, 2016 @02:52AM
(#11460271)
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.
Re:Parody O'Reilly book covers
by elcapitan on Saturday April 09, 2016 @03:51AM
(#11460411)
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.
Re:Parody O'Reilly book covers
by datenwolf on Saturday April 09, 2016 @08:24AM
(#11460967)
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.
Re:Parody O'Reilly book covers
by BinaryIdiot on Friday April 08, 2016 @11:44PM
(#11459786)
Good...or the only / expedient option?
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().
Re:Parody O'Reilly book covers
by BinaryIdiot on Friday April 08, 2016 @11:46PM
(#11459791)
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.
Re:Parody O'Reilly book covers
by matt_wulfeck on Saturday April 09, 2016 @03:01AM
(#11460290)
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
http://www.amazon.com/dp/B015YEY7FA
It's a slightly different version of the image, but still a good one.
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.
noun: parody; plural noun: parodies
1. an imitation of the style of a particular writer, artist, or genre with deliberate exaggeration for comic effect.
While splitting hairs can be fun, for all intents and purposes, I'd say this is a parody.
But yeah, I know that it is hair splitting. ;)
If anything, if you're any good at it, it shows better knowledge of your program's behavior than blindly looking around in the stack on a debugger.
In fact some of the biggest name programmers use just that -- including the very people who created .
At best it's "hardcore" -- but not "bad" or anything like what's in the list. Here's some appeal to coding authority for ya:
"The most effective debugging tool is still careful thought, coupled with judiciously placed print statements." Brian Kernigham
"I don't like debuggers. Never have, probably never will." — Linus Torvalds
Nor is there anything wrong with searching for the text of an error message, but both are funny to see as a fake book cover.
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 T-shirts: https://threddit.com/thepracticaldev
https://imgur.com/INBvStO