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

©2024 Poal.co

501

I don't know what the f is going on but I've solved about 8-9 major things there (code) and not a single one has been allowed to go in. The boss has even taken a major hit because others (everyone) knows these improvements are vital but for some mumbling reason they're not allowed to go in.

For instance -

I just found out the program was spawning new processes with "inherit file descriptors" set. Basically if the parent program had a file open, the spawned program is also holding open that file and doesn't even know it. Even if it's ie ffmpeg. The parent program has no idea which files the spawned process might have inherited so it has no way to know which files it may not be able to reopen or delete in the future.

There are a shit ton of totally different types of processes that spawn and they all are forced to inherit. Normal processes like ffmpeg or ftp programs etc. The code is obviously a generic process spawner not some sort of advanced parent process duplicator. So obviously all these processes forcing inherit was some sort of copy paste mistake.

Yet the boss says "there was probably a reason it was done that way". Brah. You're retarded but you can't possibly be that retarded. This code can not be allowed to stand and to let it is deliberately sabotaging the code.

I don't know what the f is going on but I've solved about 8-9 major things there (code) and not a single one has been allowed to go in. The boss has even taken a major hit because others (everyone) knows these improvements are vital but for some mumbling reason they're not allowed to go in. For instance - I just found out the program was spawning new processes with "inherit file descriptors" set. Basically if the parent program had a file open, the spawned program is also holding open that file and doesn't even know it. Even if it's ie ffmpeg. The parent program has no idea which files the spawned process might have inherited so it has no way to know which files it may not be able to reopen or delete in the future. There are a shit ton of totally different types of processes that spawn and they all are forced to inherit. Normal processes like ffmpeg or ftp programs etc. The code is obviously a generic process spawner not some sort of advanced parent process duplicator. So obviously all these processes forcing inherit was some sort of copy paste mistake. Yet the boss says "there was probably a reason it was done that way". Brah. You're retarded but you can't possibly be that retarded. This code can not be allowed to stand and to let it is deliberately sabotaging the code.

(post is archived)

[–] • 1 pt

>Yet the boss says "there was probably a reason it was done that way". Brah. You're retarded but you can't possibly be that retarded. This code can not be allowed to stand and to let it is deliberately sabotaging the code.

Yeah, don't start with the premise the guy(s) before you who did this piece of lame code was necessarily dumber than you... I would be you I would take what the boss said at face value, I would start investigating/double checking from there, just to be sure... Because maybe, just maybe... There's an even bigger underlying fuckery you haven't seen yet... And that's precisely because of that underlying fuckery that has never been addressed because "reason"/this-code-base-started-20-years-ago, that you have now on top of it, the lame ass code you unfucked... And maybe the ancient fuckery has been fixed since and now it's justified to pull your upgrade...

So go for archeology, search the reason beyond "uh-uh-uh the coder before ME was dumb obviously!", maybe he wasn't that dumb and had to deal with a big fuckery that shouldn't have been there in the first place and he resorted to... A hack... AKA the lame shit you found... Because otherwise, it's even worse...

...

Now maybe you're right... And what if you aren't, exactly right?

...

[–] • 1 pt (edited )

It just so happened it needed to inherit the handles to use pipes. That wasn't the problem. The problem was yet again at like a 10/12 rate I was be told an important issue I found / solved was not going to be allowed in for *mumble* reason. The boss eventually found that I was right, there was no way around it processes absolutely can not be just inheriting whatever files are currently open at the time.

Once I was allowed to commit a solution I quickly found the pipes issue and found there is a whitelist handle work around since vista. I already knew there was a possibility it was needed by something, and highly suspected the pipes being created right there, I didn't get to that stage of the investigation yet.

If you've seen the state of this code and what the two other developers have been committing in my stay here so far, trust me, these guys don't give a shit about committing code that introduces and creates all kinds of new problems. Every time I go to commit something I have to fix like 3 other issues in the vicinity.

[–] • 1 pt

Boss and under bosses, you're here to serve remember that

Choose your hard, choose your devil, choose wisely... https://www.youtube.com/watch?v=AsdYYL452C0

Spoiler: You can't be vador

[–] • 1 pt (edited )

Ya that's fine I appreciate that I have a job and work. Coding work is a bit of a musical chairs game. I'm totally fine with just getting assigned things and doing them. The torture I'm playing psychological chess in a constructive dismissal game or a "you can't out show me" game and I just need to get through 3-4 months preferably with people I could use for a reference in the future and a list of great achievements I can say I did.

[–] • 0 pt

To put this in perspective the company has actually lost a full client because a feature I was assigned AND SOLVED within 48 hours was not allowed to go in. Not only was it solved but it was solved against my bosses BEST attempts to sabotage my ability to work on the issue. He denied me access to 3 different things I needed to work on the problem at all. I had to get other people to log in to them while I zoomed with them, completely wasting their f'ing time and they were pissed.

He referred to me as "wasting everyone's time" 3 times while SOLVING IT. It's SOLVED.

So he just flat out took the issue back and hasn't done anything with it since. I have no f'ing clue but my only imagination is he is waiting until I leave on my own accord so he can make up whatever story he wants and just implement what I did and claim he did it.

[–] • 1 pt

He's trying to keep you down so you don't surpass him.

[–] • 1 pt (edited )

Hm, I see...

In most companies, it's not just about who's best at what, nah

It's mostly about who's going to fuck who, and the mega boss and the under bosses they want what? They want a piece of shit that will lick their shoes and stab anyone on demand, and will be thankful for being given those task...

It's a world of hypocrites, cowards and vile backstabbers

Never miss an occasion to shut your mouth, and keep your ears wide open... And remember; this isn't your dad's company, you don't have to give a fuck. They do shit? Encourage them, tell them they are just great... That's how it works. Don't be that guy stopping the circle jerk, the party pooper telling the truth... They don't like that... I know, it's garbage... But here's the deal; if you're in the position you're describing, it's precisely because you infringed upon the "etiquette" above... You've probably been too honest, too generous, for your own sake, essentially...

[–] • 0 pt

Go over your bosses head. Don't ask, don't hint at it, just go over his head. Do it tommorow, don't sleep on it.

[–] • 0 pt

stab your boss in the back (figuratively). I don't know shit about dick wrt coding but keep going up the chain until someone gives a damn

[–] • 1 pt (edited )

In the beginning I had to go to other superiors twice to simply just state what was actually happening behind the scenes because otherwise he was going to succeed in destroying my reputation / job. He was running me on fools errands to waste my time, when I completed it anyways to the T then not allowing it to be committed, not allowing me access to things needed to work on the task while acting like I was just dragging feet in front of others.

At the rate he's so flagrantly sabataged another employee's ability to do work that was doing great, important work and personally wasn't an issue to anyone, I could have and still could have got him fired. However to be honest I don't want to get anyone fired working somewhere just 3 months at a place I'm already getting paid half what I could elsewhere so I already know I am going to leave. He has serious deep knowledge of the code, not necessarily the smartest, maybe he's actually lost iq over time but in some ways brilliant. I don't want the person fired I just want decoupled, get excellent work done and to get through 3-4 months so I can get a new job. Or at least get an offer that let's them counter offer with a proper pay.