Whistleblower calls out IT giant over U.S. jobs (the usual H1-B visa scam)

though let me also point out that i've met extremely good programmers who were from the US, India, Ireland, Russia, Romania, Poland, Italy, etc. etc. --> and I've also met extremely shitty programmers who were from the US, India, Ireland etc. etc. ...

You are absolutely correct. In my experience when the old H-1 visa was replaced with the H-1B and alphabet soup of other guest worker visas tied to 'free trade' agreements and over riding US immigration law, the body shops such as Infosys and Tata started supplying just warm bodies, not quality, using the mantra the warm bodies were doing a job americans couldn't / wouldn't do. Resumes were [and still are being] falsified and no one checked.

It's amazing the lies bean counters and some managers bought in pursuit of quarterly profits, with no consideration of long term costs, scalability, accuracy, customer service, etc. Everyone's goal is to pass the buck and be somewhere else when the proverbial co patties hit the fan.

... Look mister.....your nonsense story has broken the BS meter. Don't waste my time.

courtesy cc to Cronos

My story is merely one of many examples of the value of experience from one of many SE's.

Cronos has summed it up nicely in post # 116:

I worry about idiots who don't have any logical thinking capability. About my projects, no. I plan those so I don't have to worry about that. And, furthermore, thanks for trying to deviate from your statement Any young professional with some intermediate skill in any of the latest technology can very well get the job done. -- that is false.

ciao, slán go fóill, farvel, alavidha, hágoónee'

One-fifth to one-tenth the pay, depending on function.

In blatant violation of the law:

"Employers must attest to the Department of Labor that they will pay wages to the H-1B workers that are at least equal to the actual wage paid by the employer to other workers with similar experience and qualifications for the job in question, or the prevailing wage for the occupation in the area of intended employment – whichever is greater." - http://www.dol.gov/whd/immigration/h1b.htm

The problem is that there are lot of legal loopholes in the prevailing wage requirement.

http://heather.cs.ucdavis.edu/Archive/CohenAndGrigsbyPrevailingWage.txt

I have more info tucked away some where.

In addition guest workers often pay no taxes or taxes on only a small portion of their income.

I dont care who you cc’ed or what you cc’ed. I have had enough of your charade so spare me your theatrics.

You came up with the most outlandish story to sell yourself as an “experienced software engineer”. You never explained what “design problem” you encountered and how you solved it. Instead you cleverly tried to pose that as a question to me. But not clever enough. The holes in your nonsensical story weren't too difficult to find. You only made a fool of yourself.

And all this time you have been ranting against overseas workers calling them cheap and inexperienced. Now I can quite understand the reason for your insecurity. If you were indeed as experienced as you claimed then you would have nothing to worry about with competition from overseas. However you are a mediocre engineer or worse a complete poser. You give American engineers a bad name. People like you screw it up for the rest of us.

Hmm... I thought you didn't want me to waste your precious time.

The story is not nonsense, but fact. Facts and reality are stubborn things. They are not contingent upon your belief in them. I politely requested that you guess what the design problem was, but you never replied.

In fact you never addressed my story other than to call it BS and nonsense. Name calling is a tactic used by those who lack facts. Many would diagnose your denigration of American SE's and the value of experience as a major case of projection.

Another fact still remains: the whistle blower is correct.

post #16

Since you have been repeatedly pinging me with your nonsensical theatrics I thought maybe I should educate you about how things really work in the corporate world.

As for the design problem....I asked the question first. And it was your story not mine. Common courtesy demands you answer first ...... but it is fairly evident you don't even know what a “design problem” is....so nevermind.

In every organization I have worked so far....... whenever there is an issue with a live system, usually the customer service is the first line of defense. Whenever there is a major fault with the system that stalls the entire process (such as the one you described) the customer service usually opens a ticket, documents the error, collect all the environment test metrics information, failure logs, fail data and all other information necessary to reproduce the error and the issue is escalated to engineering. The engineering has to go through all the log files that captured the entire event to identify the failed classes. The ticket is assigned to engineers who have either written those classes or are responsible for maintaining those classes. Only the engineers who have been actively involved in development/design of the system and thoroughly understand the internal design and function of the system is assigned the ticket.

You don't call up some Rambo/Cowboy totally unrelated/unfamiliar with the actual development/design of the system at 3am in the morning and ask them to fix the mess regardless of how vast their experience may be. That is stuff of legends, never happens ANYWHERE in real life.

...Thereafter the engineers usually have to run a bunch of tests to investigate further to determine the exact origin and nature of the error. They have to carefully study the failure logs, stack traces and all other test metrics that capture fail data and provide more information on the error. You don't go by “educated guesses”. You have to know EXACTLY what went wrong. You may have have a theory, you may have a hunch but you need to verify that by running a suite of tests and reproducing the error and know exactly what caused it before you start changing the code. The issue could originate in a number of areas such as the business rules,action classes, service classes, frameworks, middle-tier, messaging, persistence classes, data objects, data sources, queries, procedures....

If it is found to be a major design issue then you usually have a series of meetings involving engineers, PMs, and mostly importantly the stakeholders and/or customers or their representatives. The objective of such a meeting is to present all available option and weigh the pros and cons of each available options. Typically in most cases you try to hash out a “work-around” to keep the current process running and schedule a redesign for the next release cycle if necessary. Either ways its never a “one man call” as you present in your bullshit story. More often its the business impact that dictates what course of action to be taken. Engineers present their options but its usually its the stakeholders and customers whose opinion carry more weight in such situations.

From your outlandish story its easy to tell you have never actually seen the inside of a corporate organisation. You made up something totally out of your own imagination. I have conducted numerous interviews where people cook up outlandish stories narrating experiences they never had, and you are not even as good as them.

It has been my observation that people with no real substance are often the ones most vocal against overseas workers. They come online and indulge in throwing epithets and lables on some very smart enginneers from overseas. And such people like you are a huge disgrace.

This is the problem: it is the wisdom that leads to the productivity, but HR (leftists) don’t see that when they’re throwing resumes away.

This is the problem: it is the wisdom that leads to the productivity, but HR (leftists) don’t see that when they’re throwing resumes away.

Agreed.

In my experience, once upon a time it was the PM's who were responsible for getting the work done who reviewed resumes, performed interviews, and did the hiring.

Today resumes hit the circular file in HR if they don't meet the PC requirements of the nanny state, and the CHEAP labor requirements of the bean counters. On the whole PM's recognized the value of wisdom; HR doesn't.

Good Gravy!

So many words and so much vitriol in posts #127 & #128 growing out of your erroneous belief that SE’s, logical skills, programming skills, and experience are of no value.
You have completely proved my and Cronos’s points.

Hint: reread posts #114 and #116.

ciao, slán go fóill, farvel, alavidha, hágoónee’

I think your time would be better spent with some soul searching then posting meaningless commentary on FR.