I get blank all-white screens when I navigate to many useful parts of the wellsfargo.com site. The "there's a problem on our end" message pops up way to often, and "online banking is temporarily unavailable" as well. I try different browsers, mobile vs PC, it's just a horrible web site that routinely doesn't work. Why is it that we can't pull this off? Did we fire everyone in tech that works on this stuff? It's the kind of perf I expect from a tiny and failing credit union or something.
8 replies (most recent on top)
I have the same issue.
I never have ever banked with WF. Thank goodness. In the over 20 some years I have been a contractor - left and come back - and now an FTE, I have never banked with them. If you saw how their QA (well, is there QA anymore?) would look up accounts left and right simply with a name search (no social required) and how they take your check if it is an off-us one and use it in the QA lab for testing without your permission, you would NEVER bank with WF.
BofA isn't really much better. I banked with them and had check fraud. I then went to work for them and found out the check fraud was well known and was an inside job by the offshore crooks.
I was getting that on Edge, but its fine w Chrome. Even Bill Pay was throwing up a hairball on Edge.
There is zero regression testing under Agile. Does my change work? Thats the only thing you have to answer. You don't need to look right, left, up or down to make sure everything else is still okay. Then you move your code in dormant and wait two months for everything to be turned on in a release. Of course others were testing their change after you using your dormant turned off code. Everything goes live and oops occurs.
Clear your cache
...because the people running this either have been, or should be, laid off?
And you are posting this on a layoff board because…?
I’ve moved my accounts to BofA. One more account to go and I’m done with WF.