The first one is the one I had when I followed the links, and you can phrase it even more concisely: Always be looking for reasons why you are wrong, not reasons why you are right.
Works for engineering, too.
Works for engineering, too.
I may tell myself "it's impossible to use product X to accomplish this" then see that as a challenge and try to prove myself wrong. But this might only work because I can be an arrogant contrarian.
Though it seems to work better for internal thought processes than in collaboration unless you are seriously tactful.