• Dave.@aussie.zone
    link
    fedilink
    arrow-up
    46
    ·
    16 hours ago

    Always make your test messages something like, “Test message, please ignore”.

    That way if it all goes wrong at least it looks like it was somewhat intentional.

    • drolex@sopuli.xyz
      link
      fedilink
      arrow-up
      21
      ·
      10 hours ago

      I usually go with "Test. Mentioning the existence of this message can make you the target of all sorts of unpleasant things. Ignore this message or else.

      You don’t get it. You’re still acknowledging the existence of the message since you’re reading it. You still don’t get it. Either this message exists, or you do. It’s a zero-sum game. Do you enjoy existing?

      Are you thinking about it? Wrong.

      Test."

  • bulwark@lemmy.world
    link
    fedilink
    English
    arrow-up
    131
    ·
    22 hours ago

    Not quite as bad as texting all of Hawaii that missiles are inbound, but still interesting. Wonder what they’re testing.

  • FourPacketsOfPeanuts@lemmy.world
    link
    fedilink
    arrow-up
    60
    ·
    edit-2
    20 hours ago

    My first week at a major fund company I was assigned to an internal business tool used by thousands. I noticed all the company email addresses in the sandbox weren’t correct, so I ran a script to correct them. Cue a call from C-level to my boss asking why he got a “email changed notification”. Followed by another… And another… And another…

    I went out to lunch

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    64
    ·
    22 hours ago

    Oh man, I did that at a midsize company as a jr. That’s a right of passage. Informing millions of people that you’re shit at testing. That was a fun conversation with my boss

    • superkret@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      2 minutes ago

      At my first job I was tasked to create a newsletter (for customers who had subscribed to it).
      My boss told me when I’m done and he looked it over, I can send it out myself.
      Used the wrong recipient list and sent it to literally every single e-mail address the company had on file.

      When thousands of delivery failure notices, confused replies and angry demands to unsubscribe rolled in, my boss told all my colleagues to step outside the office, and then yelled at me for several minutes straight about how I jeopardized his business by trying to be a smartass and I should run everything by him first from now on. Then he called everyone back into the office and, in front of all of them, praised my initiative, work ethic, and go-getter attitude.

      All in all, it was a pretty useful mistake. We could update our contact list, actually received lots of interest in the newsletter from people who hadn’t subscribed, and I learnt that my boss is a psycho and could start planning my exit.

    • Rusty@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 minutes ago

      I think it’s a senior developer mistake. Even at midsized company developers should not have a direct access to production environment.