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

©2025 Poal.co

706

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)

[–] [deleted] • 3 pts

It has been happening slowly over time.

mega corps increasingly hire H1's from computer farms in India. No one reviews code. Quality continues to drop.

The mega tech corps are so huge that they can push absolute dog shit code and people still drink it up.

The main reason engineers suck so much today is because the consumers put up with increasingly shittier quality, then ask for more.

[–] [deleted] • 1 pt

Yeah, my friend's problem comes from the "fuck it, ship it out the door" mentality which is very frustrating. Not only did his code not run at all on my machine, it took me 2 - 3 hours to get the thing running properly, and fixing all the bugs, linter errors, compile issues, dependency problems, one class to rule them all anti patterns, and hard coded magic string/inline variable declarations. On top of this there was the issue of lack of understanding of what his thing was supposed to do, so you pretty much have to "guess" what he was thinking, because he himself doesn't have a clue how it's supposed to work. What's surprising about that, is he wrote the thing from scratch! It's like how do you not understand what you just wrote?!

I was always taught that linter warnings are compiler errors, and a lot of compilers now treat them as such. That doesn't help when the other person just straight up module configs the project to ignore and suppress all warnings.

[–] • 0 pt

When? Probably when diversity became our gayest strength.

[–] • 1 pt

Windows the original 3.1(?) wasn't exactly the paragon of great code from what I recall.

[–] • 0 pt

I bet it was more stable than Windows ME I have ptsd from that release.

[–] • 0 pt

I think I skipped that one altogether

[–] • 0 pt (edited )

You know why no one wants to work with an engineer doing software? Because they fucking suck at problem solving.

They have this obtuse, clueless mentality about what's actually important, as if the relevant things are no more meaningful than the irrelevant.

So how do they actually decide what to actually do? They fucking make it up. Literally.

What else can they do? They have no real comprehension to apply to solving software problems (which are fundamentally logic problems), so they just keep pushing shit together and then overtalk-to-fucking-death that they did something.

These little queers literally get paid for doing shit without knowing what they're doing.

No one, ever, should let some useless fucking "engineer" use a keyboard to write code.

They're fucking clueless, and fucking proud of it.

Just like niggers.

Software dev is for real problem solvers, people capable of abstract reasoning, something engineers (like niggers) struggle with at any level.

They need to stay at the kids table, while the grownups do the real work. They can entertain themselves with crayons and glitter and sparkles, until they're ready to use a wrench for the first time.

But that's not their decision either, nor should it be.

There's not one single software project in the world whose code has been improved by some aspiring nigger engineer.

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