Thread regarding Wells Fargo & Co. layoffs

App developers would have better quality code if we didn't have to spend like 80 hours doing paperwork for the SDLC/CR for people that wouldn't know what our apps do if It jumped up and kicked them in the groin. If you don't know how the apps work, or you aren't supporting the customer, you aren't adding value, you are just getting in the way.

@1vmf+1a2dqJ4H, any one in the CR process doesnt even know if the cr is right or not. Then on top of it, no one checks if only that change was done or if maybe they did more or did not do any? what is the use of this worthless process. Plus takes years to get anything through.

You know what's even worse than your accurate observation ? If you work here long enough, you start getting used to it, then it becomes routine and normal. I've bent and twisted my mind to conform to that effed up CM process. I, as the OP, have spoken these same words. Now it doesn't phase me. I've been here too long.

Change Control is the stupidest thing I have to deal
with.

@1vmf. I know what pathetic is. Defending c-appy Change Control.

You know what's really pathetic?

App teams that can't get their code right until it goes into prod/bcp.
App teams that can't be bothered to check their CR's until the day of release to find out it was arbitrated a week ago.
App teams that can't test their code and deploy new defects when trying to fix existing defects.
App teams that have no clue who supports their apps.
App teams that don't understand the difference between a pac/support group and the paging group name.

You might want to sort your own house out before calling out others that are trying to protect a multi-billion dollar earning bank from looking like we hire bottom of the barrel developers.

yea, it is pathetic and wasting company money for useless process that is broken. Cant believe people get paid to waste money like this!

I am trying to wrap my head around how agile sprints and CI/CD are supposed to work when the whole process grinds to a halt for just this reason. Also, the 10pET story is LOLworthy.

It’s unbelievable that Wells allows Change Control to be such a mess like that. No one dares to speak up. Those who are in control should be fired.

Change control in WFC is one of the top three major pain points for our team. We continuously bring this up to various levels of leadership but it goes no where. Maybe ServiceNow will help alleviate some of that, but i’m not holding my breath.

I was a tech manager / lead and had submitted many CRs over many years at WF. It's antique and departments spend many wasted hours dealing with unneeded arbitrations, the "acronym" nonsense spelling out things like SQL, or filling in details that should be clear. I once got arbitrated for noting our change would go in at "10p ET" with the arbitration note saying "what time zone is the 10p group?".

Then new rules kicked in to help (if you can call it that) with the approval process and it resulted in a pre-approval process and a couple of layers before even submitting the change.

Layoff came and I was shocked but relieved and happy to leave these dinosaur paper-pushing backwards processes behind. Good change control is actually managing the changes and not managing the paperwork.

Put more in the description/business case about the change you are making and have clear install steps with server names buildlife or jar file names , agents, and subversion urls for crissake!

Waiting until the day of the scheduled install to Arbitrate is a problem. Also, when the analyst is in India and is gone for the day causes much frustration.

ECM made up COW days and times is yet another problem.

ECM refuses to coordinate with Enterprise BCP to ensure smooth approvals for a MANDATED test... etc...

Many inefficient processes additional approvals required at the last minute. the list goes on and on.

@OP Stop cloning CR's and making lazy rookie copy/paste errors and maybe you won't have change management highlighting your lack of accuracy.

Repeat after me - spell check is your friend.

Do you have a problem with grammar and spelling? Seems to be a common theme with some people so I am guessing you are slacking in that area.

There are more important things to worry about, folks.

Don't forget to list out your acronyms because SQL is not enough, they need to know what the acronym is. Nevermind what your doing functional wise, just make sure your acronyms are spelled out. It's hilarious......