Does the inevitable backdoor attempt ever fail due to their own shitty code?
Unfortunately no, it's basic bottom bitch easy to put in a logic bomb or a backdoor that can take the whole system down, they can prove you did this in court but, since they are Indian, that will go nowhere.
Damn. Is there a surefire way to pajeet-backdoor proof your code?
Hand pick your HR and IT teams and make sure theyre on board with keeping indians out. My life goal is to run my own business so ive been looking into it.
First off this is the best way, do what DSHK said and don't fucking hire brown people in the first place. The entire reason why I'm on this site though is what happens is clueless corps pit you against them where you are actually playing god and saving the company - just look at my example with the small company where before the big team of jeets came in, I had to deal with one putting in the backdoor and having to go insane where the owner wouldn't even look at it because he wants to live in a bubble.
If working with jeets was a decision that is out of your control, there's several things you can do to get really close to preventing this:
-Don't use interpreted langs, use compiled langs. Compiled languages are better and more stable but, they require the code to work 100% before it can run. Interpreted langs only run when you hit that area of code, which means said code can be jeet bullshit and not work. Compiled langs are a great indirect way to filter out jeets dumping non-working bullshit into the code.
-Check git history like a religion. Git is a programming source code technology where you can see people's contributions line by line. Learn which area of the program jeets are supposed to be working on so you can spot them modifying other files, if they do there is only ever one reason. TAKE YOUR TIME when merging branches and read EVERYTHING LINE BY LINE.
-If a jeet is trying to pressure you by submitting their branch 5 mins before a meeting, call their fucking ass out on it and make them wait until next week's meeting to merge it. If some jeet doesn't talk to you for an entire week and then suddenly, 5 mins before a meeting, says you absolutely have to merge their shit for something to work the upcoming meeting, it's only for one reason - they dumped a backdoor or some shit in there and want to have it in now and hope you don't check now because you don't have time, then you forget about it.
-Have them work on a separate copy of the database, if they are connected to the main database, they're just gonna drop it when they are being fired. Or even drop it at some random time and just blame you. If you absolutely have to have them access the main database, make a user account that has read only access.
-DON'T let them have access to the server EVER EVER EVER and don't let them push builds EVER EVER EVER they will install a rootkit on there some of which are impossible to find even with antivirus software, and/or they will modify the code and not commit it to git. If you let them have access to the server they will put backdoors in it and this is untraceable because the code with the backdoors was never uploaded to git with their ID.
-Companies know about this and it's the reason why they invented something called pipelines, which means, never ever allow anyone but one trusted (white) person to push a build because you can bypass git and dump some shit in there and it will not be trackable. Whenever you see a company talking about pipelines it means they fundamentally know that their jeet employees are committing fraud
I think it’s funny how pajeets think they’re better because Indians make more money on average than white people. When you consider that you have Appalachia and mudsharks included in “white people” and the only Indians we allow into the US are the “top tier” of Indian society.
Indians don't make more money than white people even with the white trash included because for every 1 (fake) Indian tech CEO you've got 3 million gas station and uber workers making part time min wage or less
