• @[email protected]
    link
    fedilink
    English
    356 months ago

    I absolutely cannot stand this kind of logic.

    “We make a shit ton of money on this very critical piece of software!”

    “Then let me fix it!”

    “NO! It’s making us money NOW! It only stops making us money when it’s broken. At which point then we fix it.”

    “But that might be hours. We can minimize downtime if we plan properly.”

    "But it’s making us money NOW!1!1!”

    I shit you not I have had various versions of this conversation throughout my career, across industries, across disciplines.

    • @rtxn
      link
      English
      196 months ago

      True zen is achieved when you realize it’s not your problem. Even better when the thing eventually breaks and you can be smug about it.

      • skulblaka
        link
        fedilink
        136 months ago

        I’m not in the industry anymore, but every time I raised an issue to the boss that got ignored, I used to like to keep a little folder where I’d print the emails or just take notes about the issue, the proposed fix, and when and why it got rejected.

        Then, 8 months later when everything is on fire, I could point at the date February 12, where at 3:40 PM I raised this specific issue that got ignored.

        It never benefitted me, not once, in fact I sincerely think my boss at the time thought I was a smug little prick. Which was fair, I was one. But credit where it’s due, every time I brought the folder back out, he’d get a look like he just swallowed a mug full of cold piss and tell me I was right. That’s all I really wanted out of that folder anyway.

      • @[email protected]
        link
        fedilink
        English
        126 months ago

        It’s your problem when they can’t make payroll because of it. And it’s your problem when they ultimately blame you for not having the solution ready to implement.

        The first has happened to me once.

        The second more times than I can count.

        • Victor
          link
          76 months ago
          1. Make PR ready to merge.
          2. Mark as Draft and write in the description that management says this should not be merged until the site breaks.
          3. Site breaks.
          4. They blame you for not having a solution ready.
          5. 😎 👈 You.
          • skulblaka
            link
            fedilink
            76 months ago

            And while you’re busy making this PR to fix a problem that you haven’t been authorized on, you’re falling behind on current tickets.

            The only way to realistically make this happen at most companies is if you’re doing work for your company on off time, and, generally speaking, never ever do that for any reason unless you’re being paid for on-call.

            • Victor
              link
              26 months ago

              Yeah my joke was kind of partly inspired by the drawthefuckingowl meme. Step 1 would be the owl lol.

          • @Dkarma
            link
            46 months ago

            This is not how the real world works

            • Victor
              link
              36 months ago

              Be the change you want to see ✨🌈

      • @[email protected]
        link
        fedilink
        English
        76 months ago

        Even better when the thing eventually breaks

        You mean when it finally does become your problem?

        • @rtxn
          link
          English
          6
          edit-2
          6 months ago

          If it’s going to be your problem no matter what, start making offline backups of your email account, and print out the email conversation where the bossmang rejected the fix. Make sure your HR rep is present on every meeting, even especially if it makes the people uncomfortable.

          (this assumes that you live in a place where employee protection laws exist, i.e. it might not work in America)