Skip to comments.Whistleblower calls out IT giant over U.S. jobs (the usual H1-B visa scam)
Posted on 04/14/2012 8:14:05 AM PDT by jiggyboy
It's called outsourcing. American firms do it because foreign labor can be cheaper.
But now, one company is being accused of bringing those lower-paid workers to the U.S. illegally and that may be costing Americans jobs.
-- snip --
Palmer says Infosys, the global high-tech giant, engaged in a systematic practice of visa fraud, a charge the company denies.
Palmer said the first thing to catch his attention was an employee that had been in the U.S. from India several times before.
"He came up to me and he was literally in tears," Palmer said. "He told me he was over here illegally and he didn't wanna be here. He was worried that he would get caught."
-- snip --
Palmer says at first, most came over on H-1B visas. These visas are for people with specialized talents or a level of technical ability that can't be found among American workers.
When asked if all the people had some special expertise that couldn't be found in the U.S., Palmer said, "Absolutely not. Not even close. Many of them is what we call freshers. People that would just come over, whoever they could get to come over. Whoever got accepted for a visa."
Many of the people brought in, in fact, didn't know what they were doing at all, Palmer said.
-- snip --
When the U.S. State Department began to limit the number of H-1B visas, Palmer says Infosys began using another type of visa, the B-1. The B-1 is meant for employees who are traveling to consult with associates, attend training or a convention. But Palmer says the employees were brought in not for meetings, but for full time jobs.
Palmer said the jobs were in "Everything from coding software to testing software to fixing software to installing."
(Excerpt) Read more at cbsnews.com ...
Yeah good luck with that. I wish design requirement could be etched in stone. And good luck with refactoring data, char length, date formats.....making them talk to a java based system and trying to make them pass augments back and forth. And guess what most of the libraries handling the interfacing with the legacy systems are written in Java not Cobol. Why? Because nobody wants to tinker with the internal monolithic coding of COBOL. Thanks to the fact that no one created any documentation or generated APIs in COBOL (something you can do in Java with just one click).
COBOL you say? No thanks.
Read post #80 and #82
And dont try to convince me anymore that COBOL is a good tool. I have had my experiences.
Correction: but it WASN’T an argument over tools in the first place.
Software jobs today ARE CHEAP work. You are the one having a hard time coming to terms with reality.
The reality is:
You contradict yourself; if it were true that "US just cannot do without them" then it would be a moot point what the industry would or wouldn't "let happen." It'd be like saying, "I won't let the sun rise in the west tomorrow!"
I hope you have fun with the efficient data crunching and non-GC memory management.
But no, nothing is contradictory. US just cannot do without them AND the industry wont let that happen. Try reading again.
It’s not greedy to want to keep your labor costs down. A business’s goal is to make their customers and investors happy, not to “provide jobs.” Customers always want lower prices and investors always want higher returns on their investment.
If a business could find a way to produce its product without hiring any employees at all, that would be the right thing for them to do. Productivity benefits everyone in the society by producing abundance. That’s aided by lower production costs and by jobs that are not necessary being eliminated and those workers reallocating themselves to where their labor is needed.
I hope your rels aren’t listening to you because if they are, they’re screwing their kids over. BS is the only degree that pays anything!
sheesh, do you understand the concept of different tools for different functions? Cobol isn't good for the web front end, but the cloud computing would call a Cobol proc for batch processing because, as I said, nothing beats cobol for long-term, reliable batch processing. No oop can meet that level.
Your attitude is exactly the problem with "anyone can build it" -- any idiot can stuff gunpowder in a tube and build a "rocket", but to build something sustainable takes knowledge and experience.
So, again, your statement that an intermediate "programmer" can do as well as an S.E is wrong.
I wouldn't use Java for batch processing, nor cobol for a web page.
I've seen Java classes built by folks with very little experience not using the full functionality of oo and just treating it like a procedural language. Little experience, little knowledge leads to bad design, that leads to a code that may function but is not scalable.
yes. The opportunities are not as numerous, but when a company needs one, they pay a lot of money for an experience Cobol developer
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.