Samples fall under a different category than production systems

Question

hi
in http://www.oracle.com/technetwork/developer-tools/adf/learnmore/november2011-otn-harvest-1389769.pdf
section "How to detect browser type and version from ADF Faces" (p. 22)
Frank Nimphius writes
"Ps.: I can almost hear John Stegeman, the Oracle ADF community expert I introduce in this month's OTN Harvest Spotlight, saying that System.out.println is not what I should be using, but AdfLogger. And right he is – however, samples fall under a different category than production systems. "
Agreed, samples fall under a different category than production systems.
But, sometimes I wonder if it justified for samples to be (much) different from a production system.
First, there is not always such an explicit disclaimer on samples, to point out where significant differences are with a production system.
Sure, that is where your own skills and experience come into play, but not everyone always recognizes all aspects that should be different for a production system.
Second, why is it too much to bother to use an approach in a sample that can be in a production system?
Could this be related to the complexity of the context (tools/framework/product) the sample is being created in? If so, maybe that context should improve.
Sometimes, the simplicity of a solution a sample is intended to demonstrate, is lost when it is implemented in a production system.
Maybe it is good practice when writing a sample, to ask the question : What should be different for a production system?
Although, I currently don't have any good examples of such a "sample gap ", maybe I will update this forum thread if I bump into one.
Any comments or examples are welcome.
many thanks
Jan Vervecken

Answer 1

Thanks for the replies John and Timo.
John Stegeman wrote:
... Never use System.out.println if you are producing something for others to learn from. ...
Timo Hahn wrote:I'm with John here (even if I caught myself using SOP sometimes). ...Wow, you guys are rather strict about this.
My idea was (and is) to be lenient on the System.out.println() example, because I would consider this a minor "sample gap".
But, you are probably right (if you can find the discipline).
regards
Jan
edit : I am not saying that System.out.println() statements should end up in a production system.