Edit: so im done with my preliminary research into this codebase.

Our corporate SSO provider is changing, so I’ve been updating our tools to take advantage of the new badges. I found this in a web application that I started on today. The original developer is long gone, and according to our PaaS, this app has been running for just under 3 years without an update.

There is no CI/CD, blue-green deployment, or back ups. The database is an H2 db with ddl-auto set to create-drop on startup, meaning that this database will delete itself if the app is restaged but thanks to this guys code, it won’t populate itself. 🤷

  • sci
    cake
    link
    fedilink
    arrow-up
    11
    ·
    11 months ago

    that’s assuming they tested the backup system

      • sci
        cake
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        11 months ago

        At one of the businesses I worked at, the backup was very slow, and at some point the daily backup started taking more than 24 hours. You can probably guess what happened after that.

    • devil_d0c@lemmy.worldOP
      link
      fedilink
      arrow-up
      6
      ·
      11 months ago

      👃👈

      According to the documentation for the app, they got it classified as a shop aid tool, thereby circumventing production requirements.

      The whole app is written like some college kids hello world mvc app

      • Hawke@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        11 months ago

        [mis-]classified as a shop aid tool

        a college kids hello world app

        This hits way too close to home.

        • devil_d0c@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          5
          ·
          11 months ago

          This job pays sooo well though, so I just do what I can and try to speak up when appropriate. They never take my advice, but I have a long list of cya emails for when it all goes tits up 🤙