This was extensively discussed on HN when it first appeared in 2012:<p><a href="https://news.ycombinator.com/item?id=4273034" rel="nofollow">https://news.ycombinator.com/item?id=4273034</a>
Apart from being based on a piece of programming terminology, the twelfth item in the list seems not to be about programming at all, but rather a flagrant plug for a book.<p>How is this the first time I have noticed that?
I ran into a Yoda Expression when coding a step condition check in JCL: <a href="http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.ieab600/iea2b690573.htm" rel="nofollow">http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp...</a><p>It was infuriating because the logic is not forward thinking - if you want to check if a return code is an error (RC > 4) then your check has to be 4 < RC. The worse part was, the COND function was to test if the step was being skipped, so if you wanted to invert the logic to execute the step if the previous steps had no errors, it became 4 >= RC.<p>Edit: And because it is more of a "function" call, you can't modify the order. You MUST use it that way.
My favorites: 9. Doctype Decoration , 16. Fear Driven Development - very common these days , 20. Ninja Comments - classic!, 22. Protoduction - Hilarious! , 27. Mad Girlfriend Bug
try {
}
catch (Exception ex) {
// Gotcha!
}<p>I see this a lot in Java code. However, this does not catch all exceptional conditions, specifically not Errors. If you want to do catch everything, then catch Throwable, rather than Exception.