20 years ago. That should have been in the headline.
20 years ago? Shit, that was nothing compared to modern day amazon.
Eh, that assumes that all posts are news posts. When I first saw this headline I didn't assume it was current news, but I'm also familiar with the "Who, Me?" column I guess.
In communities like this, yes, it's generally assumed that it's current events.
That's not the precedent set by other similar, recent submissions though, - nobody complained about this other submission talking about an event in 2004 (also ~20 years ago): https://lemmy.world/post/32137161
If you want to police submitting to this community with an unwritten rule about editorializing titles to include chronological information:
It's not my favorite thing to have a few people who don't even make submissions getting upset at me for following the diabolical process of (1) reading the rules, (2) looking at previous submissions, and (3) copying a title verbatim from a reasonable source. If there's something that people are expected to follow, make it a written rule or give me access to your secret mind-reading device. This community isn't called sysadmin_news so I'm not sure how I'm reasonably expected to know this.
I’ve been a professional programmer for 19 years this year, and I caused 3-hour data loss on one of our major apps just the other week. Shit happens. Humans make errors; even experienced ones. We should strive to learn from it.
As they say:
Biting your tongue while eating is the perfect example of how you can mess up even with decades of experience.
Biting your tongue while eating is the perfect example of how you can mess up even with decades of experience.
Should have setup a staging enviroment and tasted there first before diving in. \s
Question: is the \s a Windows version of /s?
Or as we say in networking: "You're not one of us until you caused your first major outage".
(edit: typo)
Yeah I threw like 1 week of email into a black hole unknowingly.
Instead of multiple shared mailboxes for different emails they used a master shared mailbox with a bunch of DLs all pointed to it.
The DLs were just single email contact to the one master mailbox.
Well I reinstalled Azure AD Connect (no backuo config) and didn't check off the damn contacts OU.
ALL THE EMAIL WENT TO A BLACK HOLE
After fixing the issue the email was still gone. Thankfully they had an antispam proxy service that kept a copy of all email. I restored all the aliases by resending. Managed to recover sales@company.com emails and the like.
It was the most idiotic design I've ever seen. No RBAC. Everyone just had access to "the mailbox" and they had mail filters to put it in folders. They had 3k employees too. Not a mom and pop shop at all.
I feel like some C-suite complained about "too many mailboxes" and the sysadmin "fixed it".
That person should be shot. Just because you can doesn't mean you should.
You know what, one mailbox is dangerously based. The idea of 3k employees working out of a single mailbox is so entertaining to me when I dont have to support it haha. It must have caused so many outlook crashes among other issues.
Not all employees had access to it but it was sales, accounts payable and marketing... They did manufacturing but that's still too many disciplines in one mailbox.
Yeah I mean, that guy learned a valuable lesson that day. Bet he never did that again.
I once deleted a whole web server that was serving like a dozen e-commerce clients. I blame digital ocean. Both cloning and deleting had you write the servers name to confirm. Come on. Jfc. The options were adjacent.
Anyways, yep. I double check every clone/delete operation that might possibly disrupt prod ever since.
Hehe. The manager troll was perfect.
A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world