Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

334

I'm looking over some code for my friend, and the crap doesn't even compile on my machine. He says it totally works on his, so my guess is he uses a special harness with all the linter flags turned off (those are there for a reason, buddy) hence why he can get away with it. Then looking at the code structure, its horrible: mis named files everywhere, improper casting, dynamic type inference with two incompatible types. The worst, most saddening part is that compared to some production code, this isn't even the worst I've seen ...

I'm looking over some code for my friend, and the crap doesn't even compile on my machine. He says it totally works on his, so my guess is he uses a special harness with all the linter flags turned off (those are there for a reason, buddy) hence why he can get away with it. Then looking at the code structure, its horrible: mis named files everywhere, improper casting, dynamic type inference with two incompatible types. The worst, most saddening part is that compared to some production code, this isn't even the worst I've seen ...

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (9).
[–] • 0 pt (edited )

Yeah, tha shit is typical of just another fuck-up engineer.

An engineer wants recognition when he thinks he did it, and he wants control over whatever happens next when he fucks up.

And he congratulates himself for his fuck-ups.

Fascile, self-serving duplicity, and truly abysmal judgment is all they have to offer.

Engineers in sw make more work to do than they finish, because they're useless and clueless.

After you fix it, make sure everyone knows he fucked up, and how badly he fucked up. Others will draw their own conclusions from his obstinate arrogance and stupidity.