• TheHiddenCatboy@lemmy.world
    link
    fedilink
    English
    arrow-up
    128
    ·
    edit-2
    2 days ago

    So. One of the things DOGE got rid of was the CAB - Change Advisory Board. I’m pretty sure there were established Change Windows with approvals required and a documented test plan and rollback plan. Don’t need those! That just gets in the way of business! Let’s get rid of it and see how that goes!

    Yeah. We saw how it went, alright.

    Edit: I should have said it’s apparent that DOGE got rid of CAB. Because this isn’t the kind of thing you do with an Information System if you have a CAB.

    • BrianTheeBiscuiteer@lemmy.world
      link
      fedilink
      arrow-up
      34
      ·
      2 days ago

      I work at a Fortune 500 company and we have CAB meetings all the time. It’s a bit of a pain but a necessary part of maintaining stability in Production systems.

      • muusemuuse@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        21 hours ago

        I work for a health insurance company. We kept old systems going way longer than we should because costs were predictable. We reduced volatility and could throw more money at patient care. (Due to how the company was built, there’s no shareholders so we can’t hide the money there, and in our state excesses get refunded to payers every year).

        Change of guard, new boss says everything must be modern. The legacy maintenance costs are killing us. Not wrong but missing the point. They were predictable. We can manage predictable.

        They move everything to cloud shit with Microsoft dynamics and it fucking sucks. Shit doesn’t work half the time, calls keep dropping, systems are slow and unreliable, AI is everywhere it doesn’t need to be and work is of lower quality, higher cost, and takes more time/money. costs WILL explode once it’s finally working because we have willingly entered into a hostage situation with the vendor and what are we gonna do about it, move again? Security is horrifyingly bad. If you mention the words “packet capture” IT stops talking to you. They just keep buying new products to staple onto this mess that promise to solve their problems instead of hiring people who know what they are fucking doing and can say the word “no” to the c-suites.

        Spoke to someone the other day from a similar company, griping about the upgrades going very badly. They said they had upgrades they had to do too when the edict everything must be win11 came down. His companies IT dept actually fought the board and refused. They said they absolutely will not service win11 machines handling patient data due to security concerns. The board caved and funded switching that entire hospital system to Mac and upgrading on-prem systems where possible instead of clouding everything.

        Remember how everything Apple does is on a time delay? The ram cost surge didn’t clobber then as soon as everyone else. They got a killer deal on those minis.

        Once the migration was done, they spent about 30% less than expected and their downtime was minimal. IT was saying no because of the security implications. The board saw lower costs and not having to replace the entire IT dept. everybody is happy.

        I mentioned this to a supervisor. They were interested and asked what industry they were in. When I said healthcare, her eyes went wide.

        We wasted so much money on needless risk. That could have gone to fucking insulin or cancer treatments.

        • BrianTheeBiscuiteer@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          18 hours ago

          Sounds a bit like my company (thankfully we rarely hold someone’s life in our hands though). New leadership is obsessed with removing redundancies. In theory it’s a nice idea but it often falls apart when the rubber meets the road. We’re going all in on Microsoft products (started before the latest outage) and we’re not just annoyed with the migrations we’re quite pissed off at the features we’re losing from our previous products. There’s also data, propriety company information, that’s straight up going to be purged from existence because most of us have neither the time or motivation to convert artifacts into the Microsoft equivalent. 6 months later when we get asked about that research effort from 2 years ago we’ll just have to say, “What research?”

    • Rhaedas@fedia.io
      link
      fedilink
      arrow-up
      21
      ·
      2 days ago

      It seems blowing up things for progress doesn’t work all so well outside the rocket industry. I guess military, but only certain things should blow up there.

      • TheHiddenCatboy@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        ·
        2 days ago

        It doesn’t even work that well in the Rocket Industry, honestly. And Elon knows that! The Falcon 9 rocket is a stable ‘release’ that’s not experimented on. Sure, Starship isn’t, but Starship isn’t yet a production rocket. He can ask Vulcan Centaur what happens when you have a glitch in a production model rocket. That’s gonna be grounded until they find out what broke on the launch yesterday and how to fix it going forward!

        • Rhaedas@fedia.io
          link
          fedilink
          arrow-up
          8
          ·
          2 days ago

          The thing missing was that with new rocket designs you expect some booms, but you take that data and you find out why so the next boom isn’t from the same thing. Which in the case of anything they’ve touched in the FAA or other places, is not what’s happening. It’s a free for all sponsored by the prevailing administration. There was not a goal to fix and improve, but to make a show of it (at a minimum, I’m sure conspiracies abound on the real purposes).

          I often see SpaceX as a separate thing from Musk, mainly because he’s been smart enough to let them run themselves more than the other companies. And it shows.

          • Mirshe@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 day ago

            You actually want to do component-level testing instead of an all-up, so theoretically you find the thing that makes it go boom without it going boom.

            Failure to Launch is doing a large multi-part on how NASA insisting on doing all-ups with the shuttle (because it’s easier to explain to media and budget dudes than component testing) was part of what led to Challenger happening. The issue with an all-up in rocketry without the component testing before means that when something goes boom, you’re now doing a huge deep dive on production data from subcontractors of subcontractors of contractors, and whatever you can piece together from the exploded components.

            • Rhaedas@fedia.io
              link
              fedilink
              arrow-up
              3
              ·
              1 day ago

              Good points, full building to fill isn’t great, but the assumption is that heavy testing is done before that point, so the failure isn’t a known one, but to learn a new factor to design for. The advantage now is the data retrieval, everything has a sensor or camera so it’s far easier (still difficult) to find the cause. Whereas a big part of the Challenger aftermath was going off of media footage to find the spot that led to looking closer at the o-rings. There is also the issue that some were already telling them to not launch, but that was quieted down because of the focus and they didn’t want to drag it out more (without looking, it had been delayed a few times I think). So that was more a production run that pushed past recommended limits.

              • AA5B@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                1 day ago

                There’s always pressure to ship! And it’s not like there’s a sudden cutoff between safe and not safe, nor was the o-ring failure an expected scenario. Do you really hold a critical launch because someone is being paranoid about temperature?

                Being somewhat facetious with that but it’s easy to see how the wrong decision was made and I know in would not have done better

            • AA5B@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              1 day ago

              With the shuttle, you had less than half a dozen ships, all hand built. Component testing would not have been as likely

              The SpaceeX approach is all about “mass production”. Everything is componentized, everything is made to scale. They can easily component test an engine, for example, because there are always more and it is somewhat independent of the ship

    • santa@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      2 days ago

      They got rid of CAB?! We have that for technical stuff at work that would not kill anyone if there were an issue. Wow.

    • NABDad@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      2 days ago

      Do you have references for that? I can’t find anything that says DOGE eliminated CABs.

      • TheHiddenCatboy@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        ·
        2 days ago

        Oh you got me. I don’t have any proof that CAB was gotten rid of…

        …except the fact that they made an impactful change during working hours and spent hours trying to back it out with the system being down. I should have said that one of the things DOGE apparently got rid of was the CAB. Because CAB would NOT have let this happen without LOUD protestations.