Not quite as bad as texting all of Hawaii that missiles are inbound, but still interesting. Wonder what they're testing.
It's ads isn't it?
I wouldn't be able to decide how to feel if told "missiles are inbound but still interesting". Deeply in panic or unhealthily curious?
Did see that recently LA kept sending out orders to evacuate and didn’t know the cause or how to stop them?
My guess would be that their server was overheating.
Update:
you can reach our support team here
Except for Dave, who's now pursuing new career opportunies elsewhere.
Oof.
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
Rite
Your right 👍
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.
I think it's a senior developer mistake. Even at midsized company developers should not have a direct access to production environment.
Email is kind of hard. There's usually only one API key to the email client, and there's no real safe way to call it. Personally over the years my approach is to have an internal library that reads what environment it is in, and then if it doesn't explicitly tell that it's in prod, it reroutes everything to safe email addresses.
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.
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."
I just make all my test messages Dirty Harry gifs
I bet he learned more today than he did all of last year. One of us!
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
We hired a DBA that put a read lock on a production database table and went out to lunch.
That's, you've really added value!
was this really your fault then?
The "internal business tool" was a well known industry wide product that I had experience in. I should have known that changing an email address in any environment caused that new email address to be notified. It was my fault yes
This is from Montreal’s south shore agglomeration:
You're not gonna believe this but i was born in gpk haha, nice to see it here.
Pls spotify hire me. I can do these things I swear
how get such a job to earn my stripes?
That is so fucking funny.
Everyone gets one.
