We had an all hands on deck, world is ending bug one time. Like, basically the entire org got pulled onto it. In our product is a spreadsheet of activities, with dates and durations. Our customers can run a scheduling algorithm to adjust dates based off of durations and activity dependencies and relationships. This is super important. This broke. We have to make sure that activities don’t have circular dependencies, or otherwise scheduling will loop infinitely and fail. So, we basically dfs looking for a loop before scheduling, and fail it with a not really helpful error message. That loop checkimg got updated so it could properly provide helpful info in the error message. This change caused most real world schedules to have false positives for loops when checked, ergo, no ability to schedule. I found the cause of the problem but not the dependency structure that caused the issue, and ultimately decided it would be faster, cleaner, and overall better to rewrite the feature myself than to fix the original. So, I wrote the most beautiful damn depth first search of my life! Learned about the bug monday morning, had the fix good to go tuesday night, so that qa could test wednesday thursday for the hotfix merge deadline friday. Two days isn’t a lot to cover testing it, but I figure with every tester in the org pretty much available to pound on it itd be good enough. While I was working on the rewrite, other devs and qa were hunting down all the details of what happened to cause the bug, data structure wise, and coming up with good test cases. So, by the time it was ready, they knew what happened and had a much more thorough test plan. Well, it came down from on high that the fix would go into the next major release, not a hotfix, so it didn’t actually go out for 3 weeks after the monday the bug came in. Sigh. Well, I had fun writing it, and I consider it the cleanest, most beautiful and elegant code I’ve ever written. It used a stack of stacks! When I’m feeling shitty and useless at work, I go back and look at it tbh.
The act of someone sitting at a brand new Mac, with a never-before-used interface, and immediately clicking the computer icon to drag it to the trash, is such a powerful image for me.
The statement of, “this is what I think of this computer” is so strong, because I have to believe that whomever did that must have been a tech person to be at the event; but perhaps they just thought it was a shortcut and didn’t like shortcuts on their desktop so they tried to remove it? Like, you can do this with Windows… Because the computer object (in Explorer) is immutable, and any reference to it is simply a link to that object.
I prefer the thought of them just being like “this computer is trash” and doing that, and causing the system to crash.
Moments like that are why I belive in timetravel, in the real timeline it took two years to find that bug and it was resolved quietly but of course someone is going to come back and troll them by doing it on day 1.
I think it’s more like they thought they were supposed to do that. I’m guessing they had no idea what to do, and putting an object in trash or recycle is something everyone understands, so that’s what their brain told them to do.
The Mayflower brought the Pilgrims to America, not Columbus (which is also, for some reason, misspelled in the title of this post). I’m guessing OP didn’t pay much attention to their history class this year in what I’m going to assume is middle-school.
Back in the early 1990s, I worked at a small-town hardware store chain (nuts and bolts, not computers) that was computerizing. A few weeks after we rolled it out, a customer came in with two gift certificates to purchase one item.
It seems pretty basic now, but using two gift certificates to purchase one item was simply not a requirement anyone had thought of. The system had no way to ring it up. The assistant manager of the store did the smart thing and rung it up as a gift certificate plus cash for the balance, so that the customer was good to go. They had to do some adjustments on the back end for that one sale and then update the software to allow for that situation.
I always remember that when I’m working on requirements for systems, wondering what obvious things we’re not thinking of…
I can imagine thinking it’s be funny in the early stages where things wouldn’t really be too logical they way they are now. Might even assume it wouldn’t actually do anything and I could just pull it back out.
I was interviewing a couple of months ago, and one of the in-person technical interviews wanted me to write, on a whiteboard, a function that took in a timestamp and calculated the angle between the hands on a clock set to that time. After I did that they wanted me to reverse engineer the linux “tac” command for files of unknown size that I could not store the contents of locally, resulting in probably the most sinful piece of code I’ve ever written.
What really gets my goat about it, is that out of all my interviewing companies, they were by far at the bottom of the list, and was really only interviewing to get negotiating power. My company had worked pretty closely with them, so I was well aware of the poor treatment and absurdly high turnover rate, so they were really in no place to be picky. My top choice company’s hardest question was one of those basic college programming math questions where the answer is “use the modulus operator”.
A lot of the time it’s just an ego trip for the interviewer to show off how clever they are and to gloat over the interviewee when they can’t figure out some really hard problem. This actually fits perfectly with the company having a toxic working environment. When you see these kinds of questions in interviews it’s usually an indication that these aren’t the kinds of people you’d want to be working with.
People speak weird all the time, and LLMs are trained on people. Some aren’t native speakers, some just like to omit verbs, nouns, or tenses when it seems obvious and they want to be expedient, some just do it for fun or laziness (see, l33t speak and or early texting, typos).
LLMs are trained on human input, so of course it on occasion uses our bad habits. Thinking like your comment suggests is what gets people who really wrote their own stuff in trouble, because people think they can identify stuff like this more than they actually can.
You do agree that it’s a weird way of saying it though, which is all I was making fun of. It’s similar verbiage an AI would use. I get it, but lighten up lol
When I started working in the late 90s early 00s, every company had their own It-department. These days it’s just some consultant or subscription to another company offering their consultants to do specific tasks.
This thread reminds me of why having an IT department makes good sense financially - today.
You can add up all the salaries, equipment and training costs and it’ll still be cheaper than wasting time and money in meetings with consultants trying to either explain the task or moan about pricing.
Shit doesn’t work, because they aren’t paid to make shit work.
I can make code that works for me and I can make code that works for you. The price is different, but you also need to know what you actually want it to do, and I don’t know how much money you are willing to sacrifice for us both fumbling around in that equation.
The monitor disappeared rather than the computer, but we can assume the tower somewhere under the desk did as well. But what of the keyboard? It’s in the icon, yet remains after deletion!
One user during the night shift tested every possible key combination on the computer to see what would crash our software, so it became a race between the programmer locking the thing down and the user finding new holes. It ended when the user resorted to sitting on the keyboard and breaking the keyboard that got their bosses involved who told the user to knock it off.
The problem there is that you have to know exactly what you’ve done to mess it up in order to fix the bug, and when I fuck up my system, I usually have no idea what I did.
I work in QA, my colleague is exactly this guy. Breaks everything without even trying. Doesn’t even have much of an IT background, but man he’s good at breaking things.
lemmy.ml
Hot