• 1984@lemmy.today
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    I never worked anywhere where they had this set up. I would push to branches and make pull requests, but always work in the production environment.

    I was mainly working as a data engineer though so that’s probably why. It’s hard to have test environments since you can’t replicate all the enormous amounts of data between environments without huge costs.

    • expr@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      There are many strategies for maintaining test environments for that kind of thing. Read-only replicas, sampling datasets for smaller replicas, etc. Plenty of organizations do it, so it’s not really an excuse, imo.

      • 1984@lemmy.today
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        8 months ago

        No I know. But it was “good enough” for the company and we never had any serious issues working that way either. If someone pushed a faulty commit, we just reverted it and reloaded the data from the source system.

        A lot of companies have kind of bad solutions for this sort of stuff, but it’s not talked about and nobody is proud of it. But it keeps the environments simple to work with.