Ah god this gets weirder the more you look at it - also typical for AI. Like the flanges on the left sides of all the wheels, and that bizarre whatever-the-hell-it-is in the middle of the front.
I went to Olive Garden restaurant once with a friend of mine, and during dinner he made the claim that Olive Garden consumes 20% of the world’s black olive supply. I couldn’t convince him of how ludicrous this was even despite pointing out the measly two slices of black olive in our shared salad bowl.
I’m a school bus driver and we get tipped (at Christmas and the end of the year). It’s fucking ridiculous. One of my coworkers last year even handed out tip envelopes to the kids - and got suspended for it, fortunately. Imagine being a parent and seeing that bullshit when your kid brings it home.
I don’t throw away the gift cards, of course, but it genuinely means a lot more to me when I get a hand-written card from one of my kids (especially if it’s not accompanying money).
I started coding with TurboBasic. My favorite thing about TB was that you could have variable names of any length but the compiler only used the first two letters - and case insensitive at that. So “Douchebag” and “doorknocker” looked like different variables but were actually the same thing.
I got to the point with weed where the first bowl of the day made me feel great with the standard high, second bowl was meh and after the third bowl I just had tremendously negative and stressful thought patterns all the time. It didn’t help that this was all before 7 AM.
This is something that is always stated by people who are opposed to comments, but I’ve never seen any such thing in practice. If being mislead by incorrect comments is so common, there should be a bunch of stories around about disasters caused by them - and I’ve never read a single such story.
comments are for explaining why you did things a certain way
A while back I spent more than a year modifying my company’s iOS apps so that they would work properly with VoiceOver (Apple’s screen reader technology for blind people) and be compliant with FCC regulations for accessibility (and save us from $1 million per month fines lol). The thing about VoiceOver is that it’s bizarrely buggy (or was - maybe they’ve fixed the problems since then) and even when I didn’t run into VO bugs, the way that developers tended to architect these apps often made getting them to behave properly with VoiceOver extremely difficult.
I often had to resort to very strange hacks in order to get things to work, and I would always leave comments explaining what I had done for this. My manager was one of the new breed who not only thought comments were unnecessary in ALL cases but also thought comments were a “code smell” and indicative of professional incompetence on the part of anyone who used them. Whenever he reviewed my code, he would leave in the hacks (after trying and failing to fix the problems without them) but remove my comments. This resulted in many cases later of developers contacting me to ask me why some bizarre bit of code was in the app in the first place. I always referred them to my manager with an NMP (Not My Problem any more).
I’m from the camp that thinks if you’re trying to make a case (about any subject), you should start with your strongest point and work to your weakest point. Every argument I’ve ever seen against code comments starts off with the weakest imaginable points. Usually the first point made is sample code like “x = x + 1” with the absurdly unnecessary comment “add 1 to x” - as if that’s ever something that pro-comment programmers do. This video at least started off with a novel weak point (somebody using a comment with a magic number instead of making it a constant) although it’s just as weak as the “x = x + 1” argument.