10

Just got off the phone with a csr about a bug they found. No biggie, I said I'd fix it. Basically until it gets fixed I told them that when they do their process to make sure to do "foo" first, then "bar" second. As soon as I got off the phone, had to poop so I went to the bathroom, and as soon as I sat down I get a message from the same CSR, "Hey I did bar first, can I type foo then bar again?"

WTF DID I JUST SAY LITERALLY 2 MINUTES AGO ON THE PHONE. TBH IT WOULD BE BETTER IF YOU JUST DIDNT DO ANYTHING FOR 15 MINUTES BUT NOW I HAVE TO COMB CLOUD FUNCTION LOGS, FIND THE DOC UID YOU CREATED, FIND THE DOC YOU MADE, DELETE IT, DELETE THE ASSIGNMENT IN YOUR TRASH ASS WORKPLACE PORTAL, AND STILL FIX THE SAID BUG

Comments
  • 1
    Type up a response email telling them you’ll fix it, the workaround for it if they must use it now, and your (padded) timeline on fixing it. Bid them a good day.

    After you finish writing it, delete the workaround part and tell them not to touch anything, and maybe reinforce that point by hinting they might lose some of their data.

    Send the email.
    Relax.
    Fix the bug in peace.
  • 0
    @Root If only. I explained the work around, which is basically make sure this value in this field is filled out before hitting submit. The csr managed to just hit submit and then fill in the value. I can't take away the field from the form otherwise it could trigger one of the many hundreds or webhooks someone else wrote, and update other documents related to it. The bug revolved around a cloud function dying if a value was undefined, so i just added a lil logic and fixed it.
  • 1
    They've just beaten you to the poop.
    I do hope you've pooped before you went and wrote this rant.
    Sorry... I just crazy I guess. ;)
  • 1
    @AtuM Oh I did. I just didn't expect shit to hit the fan when I did.
Add Comment