I imagine a lot of big corps are in the same situation
>Hire team of pajeets
>They suck cock and send fake screenshots
>Deadline comes, excuses
>Another missed deadline, more cock sucking, more fakes
>Suits don't know what's going on and just gobble it all up
>Any criticism is brushed of as raycismsms
>Due date comes up; product is sub par (at best)
>Local team rushes to fix things up as they get all the blame and flack
>Site is down later. Suits call the pajeet team to fix things up.
>Arent these pajeets wonderful? They fixed the product in 1 week you retards needed 2 months to fix it post release. We should fire more locals and hire the pajeets.
Yes, go find my re-post of a list someone made of all the billion dollar corps that went under. The same shit I posted and showed how it happens step by step, is happening there at a larger scale.
This is what I like to call "The Indian Hop". What it means is they hop back and forth between a quantum state of the shit not working and then conveniently working whenever they feel they can use it to jump up the ladder. They do this because they know it confuses the chain of command set in place to keep jeet niggers like them out and they wait for the right time to strike. They wait for ownership or management to be on a call and then hit them with their big prepared lie.
Another story to explain the Indian Hop: I did a short stint at a company that was redpilled about Indians but in an ironic way where they were open to the whites at the company about "taking advantage of cheap Indian labor". All of the whites were programmers too but explicitly told to spend 95% of their time managing jeets, and 5% coming in to fix shit if the jeets got stuck. We had 10 teams of Indians, all of which were always brand new - we didn't keep the same jeets, you'll see why in a moment.
Literally 100% of the time, they'd do the work on track but then when we said our launch day or delivery day is the 10th - it would never ever fail, on the 8th the jeets would always always always say there was some huge sudden fucking problem, they'd be vague about it. This is what I mentioned earlier, it's "The Indian Hop". They want to have the project actually done so they can be actually secretly sure that they won't be in a real SHTF situation - but they will tell us everything is suddenly fucked up so they can just flip a secret switch they have in there and milk us more.
The owner of this company was based and we came up with a strategy: We'd wait until the jeets on a team got to 90-95% done and then we'd ask for what is left to do (this is important, hold on) and then make a big huge deal about "the big launch day" on the 10th or whatever. We'd even get the owner of the company we're working with to send a recorded message saying how big and important the launch day is and how it looks like we're gonna reach it. This was to bait the jeets because they know their salary is shit, and they will gamble 2 weeks of pay away because they think if they turn shit off 2 days before launch day, they are going to be in a position of power and be able to negotiate.
What they didn't know was we staggered the work so that the next incoming team of jeets, finished the last 5-10% that I mentioned earlier that wasn't finished. The reason why it's important to do it this way is because the jeets don't put the backdoors in the code until the last minute. You can find backdoors on your own but it's time consuming. So if the teams are so cheap, it's way better to just be pretty sure there is nothing bad in there, and then basically "shit test" them with the bait of the "big launch day".
Every single time, the jeets would take the bait, and start hitting us with creepy hollywood tier shit in that channel about how they just turned our shit off and they are going to take control of our company. We'd laugh our ass off and just let them sit there and try harder and sometimes we'd even pretend to be panicking, while we have another channel of jeets who are finishing the project. We got even smarter about this because jeets would leave their contact info in the code in the hopes the new set of jeets would call them and talk it out.
The owner and I even started to make bets on how soon a team of particular stinky to work with jeets would do it. IE, "lol I bet they'll do it at 80% with no mention of a launch day" etc. We started a little collection of the inevitable death threat e-mails we'd get once the old jeet teams figured it out - they obviously knew the company name so they'd just visit the site and see it was mysteriously completed and launched. Sometimes they'd reach out to the owner and tell some massive lie about us and the owner would reach out to us saying who are these people? We'd say we have no idea lol :^)
So take what I just said and apply it to the corporate world. All jeets do is they make a fucking edited screenshot of something 5 mins before a meeting and then claim "iz wolking yis iz wolking" and suck the roastie female project manager's cunt for a couple mins. Then BOOM 4 years goes by and suddenly as the owner you find yourself with a lack of several million dollars and not just no progress but having gone backwards because you have an entire company of people that all hate each other.
