title: Shall I use guard clause, and try to avoid else clause?
body: <p>I've read (e.g. from Martin Fowler) that we should use guard clause instead of single return in a (short) method in OOP. I've also read (from somewhere I don't remember) that else clause should be avoided when possible.</p>
  
  <p>But my colleagues (I work in a small team with only 3 guys)  force me not to use multiple returns in a method, and to use else clause as much as possible, even if there is only one comment line in the else block.</p>
  
  <p>This makes it difficult for me to follow their coding style, because for example, I cannot view all code of a method in one screen. And when I code, I have to write guard clause first, and then try to convert it into the form with out multiple returns.</p>
  
  <p>Am I wrong or what should I do with it?</p>