Oh, and the Yoda condition example isn't the classic one; the real reason Yoda notation sprung up is because of the idiomatic usage of CONSTANT.equals(variable) in Java, especially with Strings but also wrapped primitives like Integer, so that if the variable reference is null you don't get a NullPointerException. Using Yoda notation for primitives is generally not done as it doesn't read well.

Fear driven development isn't when they subtract resources from the project - it's when they add them (and normally new hires at that).