Thread regarding Wells Fargo & Co. layoffs

@tr+1jns4661y

I don’t get it. I’m an Alternate Application Business Owner and we have built our app out to where we can lose multiple data centers and still function.

And yet there are some critical app teams that somehow keep getting exempted from BCP exercises.

The smoke issue at Shoreview was the direct cause, not the final cause of the outage. What that did, though, was expose exactly how non-existence our BCP abilities and strategies were. If competent BCP capabilities and strategies were in place, the outages would not have lasted as many days as some of them did.

And it seems like Wells is cruising toward more of these.

@f8+1jns4661y Google five whys. Your response was ignorant. Same as the BCP response for the outage. Think about it.

We are months behind on due dates from "leadership" Don't care

Let’s hope so - nothing else seems to give wake up calls

@pd+1jns4661y What do you see will be the next crisis? An outage? Incomplete transactions? Corrupted data stores? Amazingly, this bank rewards its managers even when they prove to be incompetent.

@ky+1jns4661y
New DCs are already a mess and haven't migrated that much, if anything. The cloud cluster fk made it so much more has to go in new DCs (with running in 4x data centers). So b/c they planned on cloud, less was acquired and now there isn't enough storage. Neighborhoods, data halls --> cluster fk.

And yeah, we're not dealing with nonsense Saul wanted while he's over collecting his millions over in consumer.

@kq+1jns4661y

Just about everything in the history of the company that has gone wrong was the direct result of in-office work. But other than that...

@f8+1jns4661y

I’ll add there were a lot of apps in Shoreview that did not have BCP set up in other data centers to automatically failover. Additionally there were many with token BCP that could not handle the demands of running as production.

Wells Fargo tries to go cheap on tech instead of doing it the right way. He-l, not all four of the new data centers are even online yet and hosting applications and they are being redesigned already.

Reading the comments and damn… remote work at this company seems and feels miserable. Glad I like my small in person team.

Loved the comment Saul wants this. Worked with Saul at Chase and seems he has not changed. Everything is about what Saul wants all to benefit Saul

This site swallows tables...
Wells
RPA/Robotic -- 5/1
AI -- 19
Agentic -- 4

Citi
RPA/Robotic --12/34
AI -- 123
Agentic -- 3

JPM
RPA/Robotic -- 10/17
AI -- 299
Agentic -- 84

This is easier to read. If you are in tech you are getting way behind in your field. Its like keeping with Cobol/RPG while object oriented languages arrived. Or window forms and silverlight while internet and javascript came. Working on unplanned old work is not helping you get ahead.

Didn't Shoreview show executive management that the disaster recovery procedures at Wells s..cked and needed to be replaced? Since then DR has been a part of the testing process.
The simple fact is Wells is way behind other banks. Consider these open job keyword searches on the jobs at these banks (all locations):
Wells Citi JPM
RPA/Robotic -- 5/1 12/34 10/17
AI -- 19 123 299
Agentic -- 4 3 84

If you take out the non-US jobs, many of the counts above are or approach 0. This bank is way behind. Only a matter of time some crisis will come.

It wasn’t the incident it was the recovery from the incident. Heads did roll.

@f8+1jns4661y

And an exec’s head rolled. I think SVB got hired to replace them?

Replying to @dn+1jns4661y's BS comment:

The Shoreview outage was the result of a contractor performing a smoke test of the HVAC system, fairly common procedure, but they forgot to close the damper doors to the data center. The smoke detectors in the data centers detected smoke and did what they were designed to do...shut everything down and protect human lives. The hard crash shutdown affected multiple systems and apps...all of SharePoint, intranet (Teamworks), online banking, ATMs, etc.

I don't know why I keep coming back to this board to read these posts. Wells Fargo, which kicked me out 3 years ago, reminds me like an unexploded pipe bo-b. I know what is going to happen -- I just don't know when.

The tech execs here are clueless. They make demands and want immediate implementation. They verbally abuse groups when the project is red (yes projects when they lie and say we are AGILE, but the truth exists in their Microsoft Project files they demand). They get upset when issues are discovered in failover testing before an implementation is rolled out into production because they just see it as another delay instead of the benefit of such testing uncovered future critical issues that now can be avoided. They don’t understand the complexity of a lot of work and want it done fast, not correctly, engineered properly from the start.

The Shoreview outage was the result of the dismantling of the previous MRA remediations by kocksure EBCP managers. All long gone and many have “open for work” on their LinkedIn pages. Look for a repeat. Keep your down, grab the check and get out when you can.

“+1 to all this. It’s not a job—it’s abuse. This ‘SDLC’ is an anti-SDLC: ever-shifting reqs and expedited chaos fuel a gang of tech bullies (looking at you, management). Self-directed teams? Ha—they’d threaten the sociopathic spreadsheet overlords. Coders are stuck divining what the BEC wants while silos fester and outages loom.
After escaping this clusterf**k, save yourself: learn real SDLC, study product design (Cagan’s Inspired), and heal from the madness (Edmondson’s The Fearless Organization). Shoreview 2.0’s coming—good luck.”

I am glad to have a job ...

"Saul wants this."

We are all expected to operate like sociopathic coke-fueled workaholics, aka in management's image.

And ever shifting requirements with management unable to make and stick to directions forcing delivery teams to backtrack and pivot or outright abandon efforts that were worked on for months.

You forgot to add everything is expedited high priority now too.