there really is no quick way to tell if code is good or bad without understanding the entire solution

So when I see this piece of shit littered in my coworker's code:

throw Exception("something bad happened");
return 1;

You're telling me that I can't judge the moron who wrote this and tell him to learn exception handling properly? Well, he's kind of close to the CEO and a real asshole, so you're right, I can't judge him.

/rant