Oracle has a horrible reputation among devs. But I think they bypass devs for purchase decisions and straight up wine and dine and bamboozle the low information execs.<p>When I worked at a megacorp as a dev, I had near zero say in such purchase decisions. I had to work with what I was given. Thankfully I work for a much smaller shop now. Better pay and much better decision autonomy.
Is this the same Oracle/Cerner system ("Millennium", I believe) that, despite protests from the medical staff, was deployed "big-bang style" in the Swedish region of Västra Götaland, with much the same results? (And where during a press conference, where the management was explaining how nearly everything was going to plan, a doctor, who had somehow sneaked in, got up, shouted something to the effect of "you’re lying, it’s a bloody disaster!" and stormed out.)<p>(That was not an outage, though — as far as I understand the system was working, it just didn’t actually <i>work</i>...)
Title should be "Oracle execs caused five days software outage at US hospitals". If the systems helped save lots of life, you bet the engineers wouldn't be thanked for that and it probably wouldn't even be a news article
Used to work on CHS systems for Cerner. If I am not mistaken they were a "communityworks" client, which meant their databases were shared with a number of other clients - a "multitenent" envirnment, we called it. Completely bumblefucked design. Not surprised somthing like this happened.<p>Also - cerner software in general allowed hospitals to freely completely fuck up their own architecture. Sometimes ireperably.<p>If anyone has details about how this happened Id love to hear.
I think the Oracle Transaction Manager is one of the best pieces of software that I had to work with in a professional settings. Lots of other stuff in an enterprise setting is very flaky and follows trends but the Oracle internals seem very nice.