1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !uspolitics@lemmy.world
7) No Hit-and-Run questions.
Please don't delete your post for no apparent reason. If you plan on deleting a question later, say so in the post, or if you feel that you have a good reason to remove it, message a mod beforehand. It's not fair to the ones who took their time to answer, and it's not in the spirit of the community.
8) No Bots.
Posts or comments from bots, LLM's, AIs, Neural Networks, Transformers, or Marvin the Paranoid Android are not welcome in AskLemmy. Real humans only please.
Reminder: The terms of service apply here too.
Logo design credit goes to: tubbadu
Fortunately not as serious as other comments. For context, I have autism, and I frequently stim by making random noises.
One day I was at a global online meeting with very important people. I thought I was muted, so I said "MEOW".
Suddenly everybody goes quiet and somebody says "did anybody say 'meow'?"
I quickly turned off my microphone, and fortunately nobody mentioned that again.
I worked for the railways, in commuter trains. My job was to harass innocent passengers by walking back and forth and enabling them to buy a ticket should they need one. And at certain routes also check the tickets of every new passenger.
It was nice using a dialect from eastern Finland, the Savo dialect for that. It has a tendency to change plain vowels for diphtongs. It adds a kind of a "wee-wow" twang to the language. For example the word for "closet" is "kaappi" in standard Finnish, "kuappi" in the dialect spoken in Savo. The "aa" is just a long "a", sound. Pretty much the same as the "a" in the English word "car". And "ua" is pretty much like "oi" in "choir". Imagine pronouncing the word "car" with the "a" replaced with the "oi" sound of "choir" and you might get an idea of how that crazy dialect likes to mangle every damn word. And the "ar" in "garlic" would be pronounced with the same change as well. Etc.
And maybe at this point it's worth mentioning that I still had a fully male gender expression at that point.
So, we have just left the station of Haarajoki. In the Savo dialect that would be "Huaarajokj".
I enter the part of the wagon through its end door. I start shouting "Haarajoki passengers, tickets please!", but. But.
As it happens, "huaara" is how they would pronounce also the word "huora" over in Savo. And that happens to mean "whore". Luckily I noticed. So, I managed to stop myself from uttering anything further. Unfortunately, I only managed to stop after having already said the first half of that word, "huaarajokj": Yes, "huaara".
In other words, I entered the passenger wagon through the end door in the railway worker's uniform, immediately bellowing "WHORE!", and then shutting up.
Definitely an "oh shit" moment!
After that:
Me: "Hm. This station is not terribly compatible with the Savo dialect, apparently."
A female passenger: "You should have continued to the end, would have gone much less badly".
Me: "Yup!"
Tower cleared me to position and hold (back before it was called line up and wait), then cleared a 737 to land on the runway I was sitting on.
Now it was day VFR conditions and my little ship was painted bright red and white, I wasn't exactly camouflaged, but I called the tower with my entire tail number and position. RALEIGH TOWER, NOVEMBER ONE TWO THREE ALPHA BRAVO HOLDING POSITION FIVE RIGHT.
Made a great lesson for my student, the tower WILL forget about you and clear a jet 500 times your mass to land on you.
Not anything destructive (to the Company) per se, but seeing a meeting with a senior and a member of HR suddenly pop up on my calendar after weeks of waiting in limbo to be placed on a new project was definitely an OH SHIT moment.
Yep, I was made redundant 🙃
Spot welded a screwdriver to the metal sidewall when I slipped trying to discharge a capacitor. At least I thought to wear gloves.
Had a content filter server I had built. Dansguardian.
Installed some new packages, which I had wgot (joking) at / as root. Fuck, I was a dumbass kid.
After I installed the packages, I created the folder /installs and then: holy shit, mv is naturally recursive?!
mv * /installs
Well, let's ls to see if the root directory is clean.
ls not found.
Um... ok, this is a call center, seems to still be working as everything is still in RAM, but as it is working as a proxy for content filtering, you could lose the company MILLIONS, so think fast!
I rebuilt another server, swapped it with ninja speed, fixed the other server, and swapped it back with ninja speed.
And everyone asked me if I was ok. "Nothing. I mean, yeah, good."
edit: mv is recursive by default, in contrast to cp, which requires -R. Scary lesson to learn on the job.
edit 2: just in case someone doesn't understand this, I moved the entire operating system into a subfolder /installs in a production environment...
If the computer had rebooted, no one would have internet at all, as DNS would fail. Fortune 500 company. Ah damn, that was some stress.
"Hey, is everything working alright?"
"Yeah."
"Hey is everything still working? Everything good?"
"Yes, why do you keep asking that?"
No raisin.
The big annual release was coming soon and I was leading a small group of testers with after hours testing of a feature that was my responsibility to cover. It was already around 8pm and we'd been working for hours. Someone came and informed us that a specific device was incorrectly configured, thus invalidating all of the tests we'd run thus far. It was mine. What an asshole.
I told everyone to give me their devices and go home. I stayed until 2-3am running all of the tests myself. My manager video called me a couple of times and he had a good sense of humor about it, I think because I took responsibility for it and didn't burden others with my mistake. I really felt terrible but after I got the report in before the deadline later that morning, no one ever gave me a hard time about it and it just was like it never happened.
Not trying to deflect or make excuses and owning a mistake is like a super power. An imprortant lesson that has basically never failed me when I've screwed up at work.
Seconded on owning a mistake. It might get you reprimanded, but it usually doesn’t get you fired.
If it gets you fired the company culture turns toxic very quickly. I've worked for a place like that once and quit when I saw that bs.
Not mine, but another's. She stating in her Foghorn Leghorn voice "I want to say "I can't hear you over your hair. It's too bright!!" to her". As I round the corner in my short Spiked Blazing Orange hair. How embarrassing for someone.
I was asked to provide technical on-site support at an event, because I knew the underlying server system under the software that project management had found to run this customer event.
They had also hired a bunch of laptops with wifi and a router for this, which was rather expensive back then (you could have bought a small car for that rent fee alone!), so a lot was hanging on this to be a success.
Of course, I knew about nothing what this job was about until I sat in the car with the project manager on our way to the first event. My reaction was: But that software cannot do what you just told me! Oh shit, indeed.
When we arrived in the evening before the first event, the server, wifi, and one of the laptops was set up before anything else, and I went to work writing a rudimetary software from scratch that would do what the customer wanted, and finally hit the bed around sunrise.
The event was a big success in all venues on the trip. The customer was extremely happy with the acceptence of the setup by the audience and the results they got.
Tooks out search on Wikipedia. I exposed a path that can perform an unconstrained Powerset Construction concurrently on 7 servers. It filled up memory and died. User retried. While cluster OOMing.
ELI-non-IT this "oh shit" moment?
Wikipedia has a search feature. Not many people use it, but Wikipedia is huge, so enough people do. Back then, a couple dozen full text searches a second. And maybe 100 quick prefix searches.
Anyway, one thing I made for it was a way to search the wiki text with regular expressions. It's useful for maintainers.
Wikitext is the funny markup language Wikipedia uses. If you know html or md it's like that, but it can kind of "call" other pages. Whatever. Doesn't matter. It's text. And people have strong opinions about it.
You can see it by clicking "edit" (sometimes looks like a pencil) and then clicking "edit without logging in" then "source editing". Those lovely boxes at the top for a person are made with something like
{{Infobox person
| name = Douglas Adams
| birth_place = [[Cambridge]], England
}}
Imagine you have 1000 articles that use birthplace instead of birth_place. Both work, but it's driving you and all your editor friends crazy there are two ways to do it. This is believable. Trust me.
You want to find every page that has an {{Infobox person followed by birthplace. Then fix them. The nerds who came before us invented a language to ask that question called "regular expressions". The one for this looks like \{\{Infobox\wperson.+birthplace. Maybe. Nerds will know regular expressions are bad for this. But nerds will also know that regular expressions being bad has never stopped anyone from using them anyway.
One way to run these regular expressions is to convert them into an https://en.wikipedia.org/wiki/Nondeterministic_finite_automaton . You build these in memory and they are not big. But you can't really run them directly. They are pretty and fairly easy to read once you get used to them. But you can't easily ask "does this match this text". At least, not with the tools I had.
I could only run https://en.wikipedia.org/wiki/Deterministic_finite_automaton . It's deterministic! Much nicer. And you can go from a nondeterministic one to a deterministic one. Easy. Our forenerds solved the problem. You use a https://en.wikipedia.org/wiki/Powerset_construction .
The trouble is, it can make very very very big deterministic finite automata. Like, if there are 3 states in the nfa you can get and 8 state dfa. 4 is 16. 5 is 32. In the worst case. Usually you get much better. But a fairly big but not super frightening regular expression can turn into a big nfa. And the dfa would need more states then there are grains of sand on earth. Too big for computer.
So, user asked for this regular expression. The search servers tried to convert it, and filled up their memory and died. They ran Out Of Memory. OOM. The usual thing is you copy the full memory so you can look later and start the server again.
But that can take time. And sometimes people are confused and haven't set up the restart to be automatic. And they can't find you. So search stays broken for a while.
I put the localization files in the wrong folder. Thankfully, we hadn't pushed anything to prod yet, but we were trying to figure out why everything kept crashing even though our checking tool was giving the all-clear.
It was checking everything except the localization folders.
Accidental reply-to-all set on mailman list, of 8,000 users.
Only minor at about 16 minutes and 11 replies shared.
Still had a little bit of cold-sweats, and dolly-zoomed my surroundings.
I was working as a short order cook back in the 80s. One night after closing we were having a few beers as a farewell to a co-worker. We wanted some music so we taped our walkman earbuds to the intercom microphone. Came in the next day, our busiest day of the week and found out we had blown the amplifier.
At an online gaming company back in the late 90s, I deleted a file folder whose name was my first name. I had been there about a month and figured I must have created that folder for some dumb reason while I was ramping up. Turned out it was created by a previous software dev who happened to have the same first name as me, and it contained the production software. Essentially I blew away a good part of the external website.
Fortunately somebody found another copy and restored everything, named it something sane and put it in a sane place with access control.
Admittedly it was sloppy of me to delete a folder without at least looking inside it, but I really didn't feel too bad about it because standards at this place were so low - they had no concept of source control, dev/test/prod environments, or much else. Everything they did was cowboy.
Reading through the comments, I remembered my first day on my second ever job, where we were instructed to turn off computers and power strips too, at the end of the day. When I turned mine off at the end of the day, I found out other power strips were using mine, so I turned off other people's machines. Unfortunately, the guy that gave us the instructions was first to leave in the evening and hadn't have his machine turned off that way.
Also remembered that I once broke production server (maybe it didn't get to production, can't remember) by adding a single line of log, I didn't notice that what I was logging was computationally intense, so it halted everything eventually, but it was barely reviewed because it's just one log line
I'll tell you my biggest destructive moment was getting a single phase 440v/50hz motor from Europe for some equipment (I'm in the states) and it had the worst nameplate I've ever seen on the motor of whether to remove the capacitor across the two phases or not. Turns out the cap got left in only on 220v. We put 480v/60hz on it, which is within 10% so it's fine but the cap should have gotten removed. Stupidly I only hooked up to like a 30A twist-lock connection off the wall for testing before it got installed rather than the 6A it needed in the panel. The cap burned itself out, started a small fire, caught all this soundproofing insulation crap on fire. Couldn't get another motor for months. Big whoops
Decade or so ago, logging into a work computer and suddenly the screen is just tiled with the word "virus", but a bit janky looking like it was a screenshot of the word that was enlarged and tiled with no thought to whether the right side of the image lined up with the left and such - it was a very 90s cheesy movie like depiction of what happens to your comp when you get a virus, like you'd expect the next scene to be some shady hacker on the other end exclaiming "I'm in!"
Then again, I don't know jack fuck about viruses, and the machine is behaving super weird, so I unplugged the internet cable from the back, and called my manager over. He had a similar "...is this for fuckin real?" reaction that I did. Mind you, this is a hospital, so if one of our computers is fucked, this is a big deal for potentially leaking patient info, so even though it had that kind of slapstick appearance, no one was fucking around with it: so, manager pushed it up the chain, and after a few mins a fucking SWAT team of IT guys comes in and starts doing their own assessment.
After some deliberation, they start troubleshooting - keystrokes and whatnot don't seem to be responsive. One of them eventually reaches back behind the monitor and 'poof' the screen pops back to the normal login screen.
So, that facility had a fancy custom login screen, which was some generic desktop background type scenery and a wall of text that none of us ever put any thought into. One of the snipits on that wall of text was instructions on what to do if you suspect your machine has virus (which was basically what I did - leave it running, unplug it from the internet, and call IT... hooray, I'm not completely stupid!). What ended up being the cause of the "virus" tiling was the fucking VGA cable slowing worming its way out of the back of the monitor - when I got to it, that thing was hanging on by a thread, and touching the desk it was on was just enough of a bump to make it cross that line between having enough of a connection to do its job vs not. That micrometer of pull of on that cable wasn't enough to completely cut its signal, but it wasn't enough to produce a normal display either: it just picked a random spot on the screen, and filled the monitor with that repeating image. The spot it just happened to do this to was the word "virus" in the custom login text explaining what to do if you think you have a virus, lol.
TLDR, got my management chain from my dept to the top dogs running the hospital, and the entire fucking IT department to swarm to my unit over a potential data breach that ended up being a wiggly VGA cable.
Whoops.
Better safe than cryptolockered.
Mid '90s, was doing something on the company's NT 4.0 PDC. The thing about NT 4.0, when the screen locked it would show the "Press Ctrl-Alt-Del to log in" screen, but if you hit a key or moved the mouse quick enough it wouldn't actually lock and wake up again. So, as I'm sitting there waiting for the server to do something the login screen shows up. I'm in the zone, so I lightning quick give it the three-finger salute, type in the password (usa1, security wasn't super-high) and hit enter. Another thing about NT 4.0, if you hit Ctrl-Alt-Del when the machine was not locked you'd get a box similar to XP's, with options to lock the computer, log off, shut down, etc. Now, you'll notice one of the options, shut down, starts with the letter "S". And the key to press to select that option is also "S". And you'll further notice that the password I typed in also has an "S". But all is good, it asks you to confirm before it actually shuts down, right? Except the shortcut to accept that option is Enter, which I hit after entering the password. So yeah, I shut down the company's PDC. Fortunately it was late in the day and most people had already left so the impact was minor. But I was doing some pants crapping for about five minutes while the machine came back up.
The longest 5 minutes of your life.
I was working on prescribed fire as in controlled wildfire to support ecosystem function. The wind changed in expectedly. The fire jumped containment. We switch into actual firefighting mode for a solid 1/2 hour. Then the wind switches back to predictions. Problem solved. Mop up of the slopover still takes hours and it gets dark.
As we get back to the truck, keys are dropped and kicked in an attempt to catch them. There is tall grass everywhere. We search for an hour in the dark after an exhausting day for our only way to go home. Keys are found. We work at dawn the next day. Not my worst day in the office, just the least predictable.
Always carry a magnet with you.
I work in installations where vegetation is allowed to grow nearly wild, except for the mandatory twice a year cut and I've had a situation like the one you describe, with a very important key falling out of a pocket.
We also usually carry a large magnet around, to pull open iron covers. It's about 15cm wide and 2cm thick. It can pull.
The key just vanishes into the plants covering the ground. We fetch the magnet, point it into the general direction of where we think we heard the key fall and cross our fingers. We were rewarded with a very satisfying metalic ding after a few passes.
Then it was the hassle of prying the key from the magnet.
It wasn't at work, but I think someone will find it funny regardless.
During my time at university I had a web development exam for which we had to do a group project, you guessed it, making a website. This included having a bunch of different input fields, and the requirement was to properly validate each one and provide clear feedback to the user.
While adding some inputs I was focused on having all the checks in place correctly, and so I decided to put some placeholder text for the errors and do a pass later changing them with more informative ones. Which I did, but I forgot about one.
So, presentation day comes along, the professor is looking at our website, asking us to show him that we had all the checks in place and correct. He asks me to input an invalid date in a calendar widget, which I happily do, knowing I 100% had all the required checks in place. The verification runs and fails, showing the error popup I set up, which read something along the lines of:
"date's fucked, mate"
Shit. My placeholder message. Which I obviously forgot to change. I was mortified. Luckily the professor chuckled and said that technically the check worked so that was fine.
Worked in an ESA lab with cleanroom. My work had to do with plants, their composition etc.
Naturally I had to dry some plants before throwing them into the analyser, but my designated oven was occupied.
Fear not, I thought, there is another oven over there. I put my samples in and call it a day.
Come over the next day, kinda late, lab chief looks at me and is only like "ummm, you should head over to the offices and see big boss"...go over, boss guy very angry. Turns out, the other oven in the lab was reserved for ExoMars parts. Like, they disinfect the shit out of it for weeks, like, take it apart, haul every screw to the cleanroom, clean it, autoclave it, clean it again and repeat that a billion times over, certify it and clean it again. So I kinda destroyed the work of months, maybe I alone was responsible for one of the many launch delays (probably not, but I've never been told).
Arrogant young me in my first job basically just was like "maybe put a sign on it next time, lol", boss guy pauses and says "maybe you're right". So we reclean the shit out of the oven and put a sign on it. My "punishment" was to spend a lot of time in the clean room to clean some ExoMars parts. I thought "cool, stuff I had in my hands is going to land on Mars".
Fast forward some years, Russia invades Ukraine, the pipes I cleaned will never go to Mars 😢.
You were absolutely right..... Two ovens in a room, 1 for plant use and 1 that needs to be super clean for a specific purpose? A sign would have been the bare minimum, that should have been part of your lab training too.
Years ago I was working as a pharmacist in a very busy pharmacy in a city center. This was during the opioid epidemic in America and being a high volume store, had a lot of regulatory oversight on our controlled substance dispensing.
One Friday evening a young kid came in with a prescription that he said was for his grandmother. It was for a lot of oxycodone from a city two hours away. He had two girls with him when he dropped off the prescription and had never filled with us before, and wanted to pay cash. We had a policy that we didn't fill prescriptions for maintenance controlled substances for new patients >100mi from our address. We only got so much of each controlled substance so we adopted the policy so we'd have enough for our regular patients. I told him we couldn't fill it. He started to get angry and mouth off but left.
Cut to Monday which was my next shift and there is a folder with the DEA logo on the front of it in front of my terminal. I ask what it is to someone who worked the weekend and they said an agent dropped it off. I open it and the only thing inside is a business card slotted into those slits you sometimes see on the face of one of the pockets. I call the number and after some introductions the agent asks me if I was the one who denied the prescription on Friday. I confirm and the guys says that it was part of a multi-jurisdiction sting operation to catch a mid-level dealer who was buying scripts from people. He told me I wasted a bunch of their time and next time to just fill it. I told him it's emphatically my job to not do that and that I didn't appreciate him using my store since we had a bunch of other issues that local police weren't dealing without him adding to it but he just hung up. Whatever.
My heart dropped when I saw that folder though and I'm sure that is what he wanted when he did it.
Wait, so the DEA agent essentially scolded you for NOT contributing to the problem and ordered you (well, tried to) to be part of the problem going forward? What a fucking joke. If he wanted you to participate in this super important multi-jurisdiction sting he could've contacted you (as he's clearly capable to do) beforehand. The only way the agency comes out of it not looking like a clown car is if there was no sting and he was an impersonator, with falsified documents and a fake folder, looking to establish a steady drug source. It might have been worth it to report it to his boss, but maybe I'm too European to properly understand all the risks involved in doing so.
So for a game I published, there are male/female characters with what I called undermeshes, which is basically underwear that's painted onto the skin texture. By design, there is no "nudity", as the underwear is the most exposed you can get.
At the time, there were two torso 'top' textures, both created from a base design. One was a sports bra looking thing for women, and just a bare (notably not hairy) chest for men.
Things were getting crunchy and I had a few NPCs that I was trying to dress differently for a town to make them distinctive. There was an unused semi-low-cut dress asset so I put that on a single NPC, but it looked funky with the sports bra.
So I assigned the male torso top texture to the lady so the bra wasn't showing, made sure nothing scandalous was visible, and moved on.
Game gets released.
Weeks later, I'm troubleshooting a quest dialogue bug, and recalled this particular NPC has different lines (and animations!) if you're a specific sex/race.
I swap races and do the whole quest again, only to (re)discover that the reason the dress was unused was because it wasn't 100% properly set up. So when the NPC moved about with the different animations, the dress didn't move with her, making her temporarily very topless and with the bare male texture, showing a lot more than she was supposed to be able to.
In short, this is quite bad and could have resulted in a not-too-happy e-mail from Valve if someone else found it.
Fortunately (AFAIK) I'm the only one who caught it but it was a cold chill followed by an absolute panic hotfix.
I used to work at a big cable company whose name rhymes with bombast. One day I (M) found myself in a meeting with a bunch of female vice-presidents (Bombast has thousands of vice-presidents). The presenter couldn't get her laptop to connect to the big TV so I pulled out one of my gadgets and got her set up. She said "wow, you're pretty handy to have around." My brain decided that it would be a clever thing indeed to say "well, I'm pretty well-endowed in the dongle department" but when I started to say it my brain realized how completely insane a comment it was. So my brain cut me off and I ended up just saying "well, I'm pretty well-endowed" which was not exactly any better.
To their credit everybody ignored this except for one woman who actually guffawed briefly. I wasn't fired immediately so there's that.
To be fair telling someone "wow, you're pretty handy to have around" is opening the door for all kinds of inappropriate comments...
Pretty awesome you put your music on the entire building ngl. Glad you didn't get caught too.
I can't really remember anything comparable of my own, but enjoyed the read. ty OP.