So they’re having to bring in the most senior of stateside engineers to focus on a swarm team to fix the stability issues and react to them ongoing. I appreciate the approach they’re taking to fix this. It never had to happen in the first place. Displacements and offshore have an impact, and they could not have predicted this? But then we look at who the leadership is and of course they could not.
12 replies (most recent on top)
@1hby Heightened Awareness might slow it down now through EOY but it was he-l with everyone trying to get in before HA.
@1mjl. Gotcha thanks for the clarification. I was told everything was on pause due to a heightened alert.
@1nej There is still the mad end-of-year rush to install all the projects. It might not affect you directly but it's even worse than it used to be since agile has made the number of changes close to double what previous years would have.
Several years ago it used to be a race to the code freeze the last two weeks of the year, and everybody was looking to get their new code in because we were putting out really cool things for customers.
Not this year.
This year they decided to stop all releases, unless an OC 1 approval was received. It’s obvious why. The reason that I was directly provided was because they don’t want any other issues in the system that could impact customers.
If you look at the leadership of technology, not one of them really is a technologist. They couldn’t create a pivot table among the group of them, much less lead a major banking technology organization. This is where they cling to DEI so much because it’s all that they know. And they were hired to clean house. Let’s just say it for what it is.
Is this another thread about the effects we will see by cutting the COSMIC team?
I'm not in tech, but it's easy to tell that it's a mess. Almost every system I deal with has some kind of issues. My team and I waste an unbelievable amount of time just trying to navigate the this cr-p.
This all is rooted in the past 15-20 years of absolute mismanagement by tech leadership. Countless times management never wanted to hear about a better way (best practice) to design and implement something, instead it was about delivering myopic metrics to impress upper mgmt at town halls.
Add to that zero accountability for anyone, zero incentives to grow career, too many hires/fires/quits for leadership, pivoting offshore/buzzsaw layoffs, defaulting to the least minimum licensing cost of feature rich products, zero trust in allowing professionals be professionals in their areas of expertise, and on and on and on.
Then you throw a dash of Agile over the top and it absolutely, at least in my area, was implemented so poorly and continues to be so unbelievably misunderstood that it evaporated any remaining hope of dignity for the systems we have been trying to keep online.
At this point the only solution is for management to shift the culture into one that hurts their egos (but not their paychecks of course).
The technology page on Teamworks has an article about this team that was formed because of instability issues.
If you seriously have to ask what stability issues there are then you haven’t read the news in the last 90 days.
@tiy every single technology system I use during my shift is slower and less responsive than it used to be. Every. Single. One.
And they continually get slower. WF isn't going to the cloud for scalability and elasticity, only for cost management.
What stability issues? It’s possible to provide some details without “outing” yourself. This post provides no details to validate.
Because cost savings trumps all