Thread regarding Wells Fargo & Co. layoffs

@OP
I think you should google it instead of wasting time gathering mindless opinions here.

If WF customers knew their banking info was in the same vicinity as the scamming capital of the world, there would be lines out the door to close accounts. That is why WF is very subtle about the goings on, and why they threaten employees with legal action or job termination or not paying severance to keep their mouths shut. It's no coincidence that fraud in this bank exploded once that information was put into foreign hands.

@cs Adding on to my list of cons. Remembered another one:

1. For some reason, I never worked with a single one of them that could understand that copying and pasting was not the right way to do something. They could not grasp the concept of creating a common function and calling it from more than one spot. It was always copying and pasting.

Outsourcing is horrible and it's eating companies from both inside and outside.

There are no high performing companies who are outsourcing.

Typically you find it in late stage companies where moats have been established, growth is gone and now you are optimizing at the edges to extract that additional 1% margin.

From the perspective of a multiple decade experienced software engineer with about 3-4 separate projects involving offshoring groups from [the reverse of] aidni:

Pros =>

1. Ability to work while we sleep.
2. I wanted to say they are cheaper, but that's only on paper when looking directly at the expense column during a moment in time. If you actually add in the rework time, amount of time it actually takes to deliver and the quality expense, I don't think this is true any longer.

Cons =>

1. Have to hand-hold through everything. No ability to fill in details and most of the time cannot work without a full specification of every little detail.
2. The language barrier is a huge problem. Have to modify and simplify my language to be as concise and simple and no big words at all to prevent confusion.
3. The cultural barrier and approaches to work is a huge problem. They just cannot be fully truthful in a group setting. They cannot admit in a group call that they don't understand something or have not gotten something to work. You usually find out in a private message later or they flat out call it finished and expect you to fix it for them.
4. They cannot write language sufficiently. They cannot express their thoughts completely or outline anything well. I've seen 1 or 2 exceptions here, but that's less than 2-3% of them all.
5. The end code is almost never complete and almost always full of some of the most basic and egregious bugs that even a simple amount of testing could have revealed. Forget asking them to optimize anything. If its more than copying some strings from one flat data structure to another, its almost always problematic or incomplete in some way. They seem to just "give up" and expect domestic teammates to pick up their slack, and I've actually seen management vocally support this behavior.
6. At least 40-50% of the time I have to delete their work and start over to get something done right.
7. They have way too many holidays and are always sick or have internet problems.
8. The time zone disparity is a problem when trying to have a live meeting.
9. When they do speak up, the language is incomplete, imprecise, or outright wrong vocabulary or word choice. Never mind parsing through the thick regional accents.
10. They are rude and will talk to one another in their native language in the middle of a team call where the de facto language is English. I have even caught them talking bad about teammates that they assume don't understand their language.
11. Getting them to have any meaningful discussion of anything more than a basic description of what they did, what they are working on, etc. is nearly impossible. Goes back to the language/work culture issues. They largely sound like robots that can't add sufficient detail to anything in the discussion of what we are working on.

I am telling you that working with native English speakers and fellow coders have result in much much much more successful projects by comparison. I've actually decided never to work with an offshoring team again. I will outright not take a job if I find out up front they are doing it, or I will quit if management brings that to an existing project I'm on going forward. With all of the issues I outlined, I many times found myself having to distrust the work and clean it up significantly or just outright rewrite it. I would not trust a team like that to build a software project for me if I was directly paying for the service myself.

THIS
|
|
V
"If a bank advertised that it does not offshore I'd switch."

@b4 I bank with local credit unions for this and other reasons. I've never opened a Wells Fargo account despite working here close to a decade

If a bank advertised that it does not offshore I'd switch. I don't want my personal data in the hands of foreign actors.

I believe outsourcing every job in America needs to happen so all the corporate owners, movers, and shakers can accumulate even more wealth. I mean, what American citizen needs the means to work and earn a living to provide for their family ?

Instead, all of the top 20 % (we all know who this includes) needs to take all the wealth and land and leave us in the dust. We the plebs are after all

Work product is trash. Hours of operation are trash. Can't understand a word in meetings. Other than that it's going great.