As long as the different conditions don't have side‑effects. Otherwise using condition 1 may modify the behaviour of condition 2.
You can get the same slight advantage if you put the condition more likely to be
false left of the && operator or right of ||.
There are some instances where it is necessary to oder
test, etc. If you use getClass() in an equals method, you must have the null test before it.
If you have those terms in exactly that order, you can be sure that if it compiles it will run free from exceptions. The test for
ob == this goes first, not because it is more likely to be true, but because it is very fast and can short‑circuit the method so the second half is never called.