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

©2025 Poal.co

146

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).
[–] [deleted] • 1 pt

I noticed this in this person's code, sure it "works" but at a cost of being an unmaintainable pile of absolute garbage. It was so bad that changing a variable name killed the app in 30+ places. And then there was the very tightly coupled dependencies everywhere, which made no sense. The thing is this isn't the first time i told this guy that this code is trash but he always comes back with some excuse like "well it works", "why you so mad, bro?", "Just ship it first, we can clean it up later (lol)", etc.

The end result is that the entire thing ends up needing to be completely rewritten anyways. in this case, his choice of technology was also ... interesting. It wouldn't be my first choice, and upon reading the docs for what it is he tried doing, he was using an older, deprecated library that had a name change, hence why the code documentation is so sparse. What ends up making this even more frustrating, is the engineer in this case punts it to someone else (me in this case), who fixes it, and then pats himself on the back at how great an engineer he is.

But all the efforts to fix the platform by someone else are completely ignored. This isn't the first time a non coding engineer arrogantly assumed that all the "fixes" required were minor crap that didn't matter.

[–] • 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.