I disagree. Using this technique will lead to more cyclomatic complexity. I aim to write small methods and readable code. In small methods, there is no problem using early returns. Early returns will also help in the readability, because you can stop reading as soon as you realise, that the method returns here, whereas you have to read the whole method in order to know if some other code is executed.
Lots of extra comments here:<p><a href="https://lobste.rs/s/z17zyg/structured_programming_how_write_proper" rel="nofollow">https://lobste.rs/s/z17zyg/structured_programming_how_write_...</a><p>Like several of the commenters there, I also think that early returns are actually a good pattern. (I also happen to think that throw and yield are perfectly fine. )<p>If you know that your method is never going to work out anyway today, abort immediately. Don't hang around!