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

©2024 Poal.co

991

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)

You are currently inside a comment thread.
Click here to see all the comments (11).
[–] • 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.