Live data from Hacker News

Car allergic to vanilla ice cream (2000)

cs.cmu.edu

201–210 of 517 posts

Re: Car allergic to vanilla ice cream (2000)

#201

> Moral of the story: even insane-looking problems are sometimes real. To me the moral of the story (and my experience) is: user's problems are usually real, but don't trust their ability to diagnose the actual cause.

Indeed. A timing problem was my first thought when I read the title which was obviously provocative, maybe that's because I deal with timing problems often so I got lucky there, but I rejected the idea, thinking the user would have noticed it too. Nope.

I used to do some help desk as part of my dev job, and from my experience, users easily assign any random fact as the source of the problem. Often things like "correlation is causation" or *post hoc ergo propter hoc" (after that, therefore because of that). Good as heuristics, but bad when they are substitutes for reasoning.

Users cannot diagnose at all because they have no idea of how the thing they are using works (which often normal - we are the engineers, they are the users) (in this regard, users that think they know "that stuff" are among the most difficult to deal with). One cannot properly diagnose something one doesn't understand well.

Re: Car allergic to vanilla ice cream (2000)

#202

Earlier quoted context omitted.

Definitely an urban legend at this point. A reddit thread[0] mentions it being collected in 1990 from computer stories going around in the 80s[1] [0] https://old.reddit.com/r/talesfromtechsupport/comments/5yrs1... [1] https://www.goodreads.com/book/show/3227607-the-devouring-fu...

Essentially all these stories are apocryphal. Even this vapor lock story. Sorry but even before today, having a automotive engineer sent to a random person's home over what clearly sounds like a quack letter seems implausible to me. The dictates of capitalism, human resources, and the politics of the workplace would make this difficult if not impossible. Even in the past when there was more human capital in support p…

Every now and then a ceo will do somethings like this. If this is true idk. Good for PR.

Re: Car allergic to vanilla ice cream (2000)

#203

Earlier quoted context omitted.

I'm going to armchair and guess that your brother needed a new battery. My (GM) car gets really funky startup behavior when the battery gets old. It will often turn the starter fine, but the electronics can get stuck in weird states until I disconnect the battery (essentially a hard reset).

If it was surrounded by a crowd of engineers, surely someone would have tested the battery?

A friend who is an automotive engineer shared once that most colleages were not so great with cars. Engineering new cars is one thing; fixing them is another. It's like asking a programmer to do system administration - two different jobs.

Re: Car allergic to vanilla ice cream (2000)

#204

We had a similar problem at work in the late 90s. A member of staff reported that their mouse would stop working between certain hours of the day. It had apparently been okay in the morning, stopped working over lunchtime then started again later. On some days it would work perfectly all day long, but on others it would stop working between those hours. The biggest clue was it would always work perfectly on overcast…

Reminds me of a problem that I had (many years ago) with my iPhone 4 - if I tried to boot it in a dark place, it would get stuck on the Apple logo in an infinite boot loop.

Turns out some versions of the Pangu jailbreak for iOS 7.1.x would crash during boot if the reading from the ambient light sensor was below some threshold. To this day I don't know the exact explanation of this bug, but it seems that Pangu included some unnecessary code that messed with the light sensor [1].

If you don't believe me, there is a huge reddit thread[2] with a lot of people confirming this.

[1] https://www.reddit.com/r/jailbreak/comments/294wob/jailbreak... [2] https://www.reddit.com/294wob/

Re: Car allergic to vanilla ice cream (2000)

#205

Yeah, that isn't how this works. Popular things are closer to the back of the grocery store -- milk, eggs, meat, produce, higher-volume soft drinks -- in order to force you to walk past everything else to reach them. Ice cream is not that popular, so it could reasonably be stocked near the front of the store. But all the flavors are stored together, as you'd expect. Engineers who make house calls are also not a thing…

> Popular things are closer to the back of the grocery store -- milk, eggs, meat, produce, higher-volume soft drinks -- in order to force you to walk past everything else to reach them.

> Ice cream is not that popular, so it could reasonably be stocked near the front of the store. But all the flavors are stored together, as you'd expect.

This part is actually more plausible than you'd expect, especially if you assume that details are slightly garbled by the N'th retelling.

Last year, we went to a convenience store to pick up some ice cream treats after a big hike. There was one of those mini freezers with a set of frozen treats right next to the entrance, facing the cashier. But there was also a line of full-sized freezers containing all the usual frozen goods (including frozen ice cream treats) in one of the aisles. Depending on which frozen treat you wanted, you'd either be picking it right up by the front door, or having to wander down an aisle to find it.

Re: Car allergic to vanilla ice cream (2000)

#206

We had a similar problem at work in the late 90s. A member of staff reported that their mouse would stop working between certain hours of the day. It had apparently been okay in the morning, stopped working over lunchtime then started again later. On some days it would work perfectly all day long, but on others it would stop working between those hours. The biggest clue was it would always work perfectly on overcast…

Had a similar effect with garage door sensors and TVs which use infrared. During sunset, the sun would line up juust right to blank out the sensors

Re: Car allergic to vanilla ice cream (2000)

#207
post #165

Earlier quoted context omitted.

Another similar anecdote I heard before was related to a wireless device, and some employees flying a drone during their break, generating interference.

My parents have some old Gateway amplified computer speakers. Came with the 386! They still work perfectly... except for a regular pop of noise every few seconds that would intermittently show up, that scaled with the volume setting. It turned out, their portable phone (read: landline with short-distance wireless RF handset) would ping from the base station to the handset, if it were off the cradle, which was being p…

Remember how old speakers would let you know if you were about to get a cellphone call. It was like digital precognition haha

Re: Car allergic to vanilla ice cream (2000)

#208
post #36

My wife's car right now is low on windshield wiper fluid. It warns us at a particular spot while we are driving. Not a particular distance from home, a specific geolocation. First thoughts were that it was the amount of time as she went to something and came back. But it does the on screen and audible warning at that location every time, no matter what was driven before that, whether it was 5 minutes, 5 miles, an hou…

Sounds like an area with strong EM interference. Maybe a stop-light with those underground sensors? or under a high-power line? or near a power transfer station? or high-power radio antennae?

Could be giving just enough weird EM interference to bump the sensor from "enough fluid" to "low"

(I know I sound like Scully from x-files but could just be?)

Re: Car allergic to vanilla ice cream (2000)

#209

We had a similar problem at work in the late 90s. A member of staff reported that their mouse would stop working between certain hours of the day. It had apparently been okay in the morning, stopped working over lunchtime then started again later. On some days it would work perfectly all day long, but on others it would stop working between those hours. The biggest clue was it would always work perfectly on overcast…

I had a similar problem, but in the opposite direction. My cable internet speeds at home were fairly good (for the US, anyway), but sometimes would absolutely bottom out. Not dead, just glacially slow. After troubleshooting everything under the sun, I came to realize that the problems would happen not when it was raining per se, but when it was heavily foggy or misting. Normal to heavy rain was fine. Called the cable…

on dslreports or broadbandreports there's at least two instances of me complaining about two cable companies because, at last, it was figured out there was moisture ingress in the LE (line extender, usually on cable lines on poles). The only common denominator was it happened during prime time, every night, and went away around midnight.

The other common denominator was the cable company refusing to believe it was an issue with their equipment; this meant it took a couple of months of calling them every night until they finally sent a technician and a manager to my house to verify that I wasn't wrong, leaving my house, coming back 15 minutes later to say "it'll be fixed tomorrow, there's a problem with the LE balance up the road" - and then the issue is resolved.

Now this doesn't sound so bad, until you learn that the first time this happened to me, i had only VoIP - so the internet would start to foul, i'd call the cable company, and the tier 1 would reset my modem at some point, and then i wouldn't be able to call back until after midnight (or whatever), when there was no longer a problem. So after a week of this, i would walk 30 minutes - one way - to a pay phone (remember those?) once the internet slowed, call them, explain that i couldn't do anything they wanted me to do physically, since they disconnected my phone line every time i called.

This is what happens with a de facto monopoly.

I will never pay suddenlink another dime, even if they're the only terrestrial provider, for whatever reason.

Re: Car allergic to vanilla ice cream (2000)

#210
post #40
post #2

This reminds me of a GM minivan that my youngest brother-in-law drove, back in the '80's. He'd gotten it from his father, who was a career GM automotive engineer - and complained that, occasionally & randomly, it would not start. It seemed like the minivan's whole electrical system was dead... Brother-in-law was known to be "not so good" with cars - so his automotive engineer father didn't take the complaints serious…

I have a 2009 Mercedes SLK that had the same symptom. It was absolutely fine 99.9% of the time, but one time in a thousand it wouldn't even try to start. No clicks, no indication that it even knew I was in there turning the key. Just dead. And then seven or eight hours later... it would start fine, as if nothing ever happened. Couldn't correlate it to anything. Had it towed to a service center a few times when this h…

That definitely sounds like a loose connection, not an ECU problem. Usually it's a bad clamp on the battery terminal. Often it's the ground clamp in particular.

The easiest diagnosis is to rotate the cables on the terminal several times to rub off oxide build up, then leave them in an orientation so that the natural tension of the cable forces the clamp into good contact.

A "dead" (low voltage) battery will still cause some indicators/lights to come on when you crank, while a bad connection usually acts like zero volts.

Post reply on HN