It depends.
If you're following a convention of early returns to handle error cases then that's good, if you're just doing arbitrary things then it's bad.
The most serious problem with the code as presented is that you're not using curly braces. That means not quite understanding what clarity's about. If not for that I'd just answer your main question with "aim for clarity", but first you need to understand clarity. As first step on that road, start using curly braces. Try to make your code readable by others, so much so that it can be understood at-a-glance by someone else (or by yourself months/year later).
Cheers & hth.,
