Thread regarding DXC Technology layoffs

When will people figure out

The faa and united outages can probably be traced back to the rubbish work done by DXC. The legacy infrastructure being maintained and mainframes need to go soon and DXC is going to lose more revenue. Surprised they have not been sued for negligence yet


by
| 29 views | | 5 replies (last 2 days ago) | Reply
Post ID: @OP+1m7mxbe6j

5 replies (most recent on top)

In business you can either do it well. Or you can do it cheap.

The problem with cheap is there is always some cowboy willing to do it for less, or some grad intern willing to do it for free to get a foot in the door. Oh and AI that can do it better than anyone and currently as long you do it slowly enough you don't have to pay for it to solve any problem you have. Whether it works is a different matter, but I'm sure they can still get there quicker without any of DXC's bureaucracy in the way.

by
| | Reply
Post ID: @eq+1m7mxbe6j

@cg yawn. This is a worn out joke. Try harder.

by
| | Reply
Post ID: @cy+1m7mxbe6j

The solution to all of these is the path breaking and innovative strategies that we have put together for a while in place - it is platform dxc - platform x - AI infused oasis to ensure that client systems get automatically upgraded and patched and secured with zero downtime. Only we have that technology and the experience to execute.

by
| | Reply
Post ID: @cg+1m7mxbe6j

FAA outage was L3 Harris...

United, I don't know yet.

by
| | Reply
Post ID: @bc+1m7mxbe6j

Who actually started the strategy of it's best not to upgrade because something might go wrong?

I find it increasingly difficult to convince clients to upgrade anything. And when they eventually do, they often don't choose DXC to implement it or maintain it going forward. So the general policy of leaving everything running exactly as it is simply continues.

Until, of course, it doesn't.

Huge parts of the commercial world are running on legacy infrastructure. Not necessarily because it's the best solution, but because upgrading is considered too expensive, too risky or simply too difficult to justify.

There's also an interesting perception around failure. If you leave a 20-year-old system running and it eventually fails, that's unfortunate. But if you attempt an upgrade and something goes wrong, suddenly you've created a problem that wasn't there before. So don't mention it, you can't be blamed, it's the clients problem - it's their system.

The irony is that the longer you leave things untouched, the harder and more expensive they become to replace. Skills disappear, documentation becomes outdated, dependencies become obscure and eventually the people who originally built and understood the systems have moved on or retired.

Meanwhile, the business continues to rely on them.

I sometimes wonder whether organisations are actually managing their IT infrastructure, or simply hoping it survives long enough to become somebody else's problem.

by
| | Reply
Post ID: @a6+1m7mxbe6j

Post a reply

: