• 2xsaiko@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    77
    arrow-down
    1
    ·
    1 year ago

    Their source code management must be an absolute disaster for these kinds of things to keep happening.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      14
      ·
      1 year ago

      I can see compiling happen accidentally, since it’s probably just a compile flag and someone forgot to disable it. But pushing is really surprising, sure it can be automated, but usually you have a manual process for such things (e.g. my company’s prod deployment is 100% automated, except for a manual approval step once everything is ready).

      So the only way for this to happen imo is if they pushed something intentionally and has accidentally disabled/enabled a flag at some point prior.

      • tourist@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        ·
        1 year ago

        It may very well have been two or more different people stepping on each other’s feet in the dark.

        I recall binge-ing Source leak summary videos. Everything that Valve uses that engine for is extremely tightly coupled.

        Whenever CS:GO or Dota 2 gets an update, data miners get to work and discover a bunch of assets of unrelated source games.

        Sounds like your company is doing things the halal way and using modern standards. At Valve, it’s just a clusterfuck dev tool GUI on top of a monolithic codebase where no one can possibly know a fraction of what’s going on.