Fix one defect and at least one other system breaks. The quality of work in this place has somehow dropped from how low it was before Charlie's reign of error. How much more incompetence through RIF is WF willing to accept?
WF is the Boeing of the financial world.
Tech survived on brute force in the past. Now, we survive (if you can call it that) on pure luck. Suffering outages and customer impact along the way but we’re just barely fast enough to mitigate the situation.
There have always been tiger teams, on-call, quick reaction teams, etc but have you noticed that singular points are never the solution anymore and it’s generally a “as many hands as possible respond now!!!!!” type situation? We’re so short handed and scrooed basic skillset-wise across the board that you have to shotg-n respondents to solve an issue vs trust that anyone responding is good enough.
'Good to Go' + PCCA are good in theory but HORRENDOUSLY documented. They are supposed to dovetail with 'branching strategy' which is also just an overkill for most workflows and a mirage for which no coherent documentation exists.
1 step forward, two steps back as any potential time savings of these are lost to researching the possible causes underlying a vague error message...which most likely needs some sort of pointless hack to work-around and 'fix' a problem that doesn't even exist.
The inevitable repercussions will become fully evident only after the parachutes have been deployed.
@btw Commit code? They always want Stateside to do the commits. After all it was "our" problem. They want to remain angels. Did they ever get the standard, WF branded Angular library out for .NET? Thats the other thing.... .NET or Java?
Hudson Yards doesn't want anyone in the US to think of WF as a "great place to work", they want us to leave, preferably without a severance. Being a great place to work doesn't advance that agenda. Have a candy bar, get no raise when you do get promoted, go to the office for no reason at all, and prepare to get outsourced. That's their only plan.
I m seeing few new software engineers hired in India who doesn’t know how to commit code :) I mean WTH is this.
So should TK be called out in her hometown as the job ki-ler or a socialist for sending jobs offshore? Maybe a hometown protest or calling out in public or wherever she goes , being noted as a destroyer of jobs and enemy of the workers.
Before I left I had to train Ind engineers on the system I had just re-engineered and converted to the cloud. The system developed a nasty habit of populating its combo boxes from SQL instead of using its Redis cache. Redis is used since there is no such thing as "private memory" on the cloud. Anyway, the "problem" was sent around to about 6 developers. Here is what I found:
The other systems to be converted (about 17? in all) were given to M$ft consultants to "convert". These systems were better engineered than the one I converted. Instead of truly converting the systems the M$ft consultants half converted them to work on a "special" Azure library they had. The systems at Wells are done by people "winging" it. That's how you get to PE and DE.
Wells is the only place I left leaving a sh..t pile. Wells needs to start over.
Hard to be dedicated when you see jobs moving to India. Even worse when you have to work with your “coworkers “ in Bangalore who know nothing and do even less but don’t seem to be accountable. If I didn’t actually do work or seem to show up I would be fired. These guys seem to be ghost employees but we have to pretend they are resources on our team.
@wvo this is me several years ago. Quietly quitting. Ducking for cover. It is interesting to see how some of the toxic engineers have become "principal engineers" and "principal engineers" become "distinguished engineers". Does WF think they are a tech firm?
@swr you still have Pluralsight .. don't you? Everyone should upskill while quietly quitting. Isn't that what M. Rider did a few years ago?
@hsf the outsourcers will stare at their belly and dream up ways to improve tech.
Only a select few in tech are allowed to be decision makers, be true professionals in their field. This is all new hires/fresh blood (no one gets promoted).
The majority of everyone else in tech who's been with the company feel neglected. These are good people who work hard and continuously demonstrate full competency at their current jobs. Since WF doesn't promote, managers are afraid of not being able to replace their treasured people. The trap is set.
So we have really excited fresh blood getting their pay and making decisions and being introduced as someone who works remotely while the existing office worker bees are justifiably unmotivated as the bank has not given them anything to look forward to.
Difficult to delivery technology well and at a large scale when there is this severe of a dichotomy in the workforce.
It's all on WF to sell themselves as being a great place to work for everyone. People need to know what metrics to hit, what types of ways motivated employees can get recognized in order to stave off boredom and be given new roles, new challenges.
Until that is figured out, the technology in place today is a reflection of how the people behind it are being treated.
Tech guy here. The “leadership” has ran off some really good people. Others have left for greener pastures. The only ones who remain are the ones who are no good, and the ones like me - who are just waiting for the inevitable layoff to jumpstart their retirement.
More outsouring will improve it.
I second that, the lack of basic skills in tech is alarming.