https://www.moreno.senate.gov/press-releases/new-moreno-bill...
https://www.moreno.senate.gov/wp-content/uploads/2025/09/The...
And that also doesn't solve the problem of dealing with institutional knowledge loss if you decide to aggressively cull employees trying to unionize. In either scenario the solution is for union workers to become even more aggressive with their demands and force companies to acquiesce.
With pure offshoring, you do have control over who you pick, what their mode of work is, whom to fire, etc.
With outsourcing to offshore, the local company hires people, usually on the cheap, to only just fullfill your contract and no more. If people underperform, you may complain, and maybe they'll be moved to a less prominent and visible role, or maybe they'll be shuffled to the next customer of theirs. So things will be bad, because it is not in the interest of the local company to do one iota more than necessary. And you'll still have to have your own QA, architects, etc., to make sure you at least get what you paid for.
Every outsourcing effort I have seen at some of these massive companies has been pretty tragic, where the best that can be said is now there is a shit but cheap option to be used where the quality doesn't matter.
This gets repeated across all the entrenched players simultaneously, while the product quality stagnates or declines (but the stock goes up).
Is it? If it is a disaster , why there are millions of IT folks employed in offshoring locations?
Only the cheapest offshoring ends in disaster. Cheap contractors from TCS will fail you. Open your own dev center, hire few thousands engineer there - a road to success. And yes, no one will actively complain about RTO policies there.
