• rwhitisissle@lemy.lol
      link
      fedilink
      English
      arrow-up
      17
      ·
      10 months ago

      I’ve written poorer documentation than this.

      “Here is a work around to fix [weird bug in production]:”

      “Edit: Disregard the above. It fixes [weird bug in production] but causes [bad thing] to happen.”

      “Edit 2: Apparently the first edit is wrong. It doesn’t cause [bad thing] to happen. Bad thing just happened to occur simultaneously the first time I did the workaround.”

      “Edit 3: [weird bug in production] has been fixed. This workaround is no longer needed.”

      “Edit 4: Turns out [weird bug in production] we fixed is what allowed our systems to communicate with one another. Had to rollback change. Work around is now considered ‘the fix’ going forward.”

      “Edit 5: Turns out it DOES cause [bad thing] to happen, but [bad thing happening] is a core component of our system’s design and also PAYROLL NEEDS IT TO FUNCTION?!”

    • doctorcrimson@lemmy.today
      link
      fedilink
      English
      arrow-up
      11
      ·
      10 months ago

      Did you read the Documentation?

      Yes and I followed it exactly by running the Feldisprut command with the 8 parameters

      What are your parameters?

      Feldisprut -i -p -87 -256 -codecreplace -codeccopy -withsound -biflwop

      Why are you using biflwop?

      MY GUY I DON’T EVEN KNOW WHAT IT IS I’M JUST FOLLOWING THE DOCUMENTATION. Tried it without biflwop and it says I’m missing a parameter, so what do I put there?

      use “nobiflwop”

      No changes

      Oh, right we don’t support 256 on the beta, it only goes up to 128.

      Fuck you.