Live data from Hacker News

The code worked differently when the moon was full

hanselman.com

111–120 of 175 posts

Re: The code worked differently when the moon was full

#111
post #91
post #38

I heard a great story a while back for a digitization project where historic content was being provided by many libraries around the world, including one in Russia. The quality of the scanned books was excellent, except for a weird distortion every so often where part of the page would be shifted partway through as if someone had shifted half the page in Photoshop. This was only noticed in books over a certain size s…

This is why you see sensitive imaging equipment in labs on air tables. Sometimes the entire room is an air table.

Not a native speaker so I didn't know what an air table was. But since I've worked in labs, I recognized it from the picture accompanying the Wikipedia article:

https://en.wikipedia.org/wiki/Optical_table

Re: The code worked differently when the moon was full

#112
post #26

We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…

preemptivly storing images from camera of rejected samples would have saved everyone more time, as it would be enough to review images of failed samples and notice a flare. of course if that was an option.

Re: The code worked differently when the moon was full

#113
post #66

Earlier quoted context omitted.

The end of that article is a good reminder of the units command, I've been using Google for units conversion for so long that I forgot about the standalone units . It even comes standard with OSX.

Is there an equivalent command for doing things like 147 days from today or days since 21 jun 2021 or 88 days after 15 Aug 2021? This is the one thing I really wish was in Spotlight (I use spotlight for unit conversion and calculations which is really handy).

To clarify, I was thinking a quick command line thing. Right now, I do it in a browser (both DuckDuckGo and Google produce the answer easily enough).

Re: The code worked differently when the moon was full

#114
At my work they had a server outage every so often, where it seemed to just go down (back in the 90s). Turned out the cleaning lady came in the evenings when there was no one there, unplugged the server before plugging in her vacuum cleaner. And then plugging the server back in.

Re: The code worked differently when the moon was full

#115
post #10

Tangentially related, here's another fun bug that inexplicably cares what time it is: Open Office cannot print on Tuesdays ( https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161... )

A bit unrelated, but another fun one, "We can't send mail more than 500 miles": https://web.mit.edu/jemorris/humor/500-miles

The "magic" switch: http://www.catb.org/jargon/html/magic-story.html

Re: The code worked differently when the moon was full

#117
This reminds me of something I lived through as a nerdy teenager working a summer job as first line IT support at the headquarters of a multinational, in the mid-90s...

One day, I started receiving calls (through my pager!) from rather many people about intermittent networking problems. The state of the art 10mbit wired UTP network would have frequent bursts of 90% package loss.

What was weird: only people on the fifth floor would have this issue..!? Our first thought was that they were on a single hub/switch that might have broken. But no, they were connected to the same uplinks as the computers on the problem-free surrounding floors. Furthermore, laptop users (who were of course also wired at the time) were reporting no problems whatsoever.

We were pretty much out of ideas by that point, but did an experiment just to test our assumptions: we took a PC and hooked it up with a long network cable and a power extension cable on the fourth floor and started pinging it. Flawless. Then we started walking up the stairs, and, yes indeed, somewhere around halfway up the stairs packets started to drop. (But not at all times, sometimes it would be fine, like all PCs on the fifth.)

If you want to guess at the cause, this is your chance. :-)

We brought in a company specialized in EM interference. It turns out that a GSM antenna placed on the roof of the four story building opposite to ours about half a year ago, had just been turned on. Its height aligned to our fifth flour. Whenever someone was using this mast to make a call (which certainly wasn't all of the time back then), it would cause interference on a specific model of network card that we were using in all of our PCs. It had a relatively large metal component that was apparently a pretty good 900 MHz antenna.

When confronted, the mobile operator quickly adjusted the antenna to not be directed at us. I believe all network cards were replaced soon after. Fun times!

Re: The code worked differently when the moon was full

#118
post #26

We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…

This is like a real-world equivalent of the "cleaning lady unplugged the machine" urban legend.

I know someone who had that happen to a server he was directly responsible for (well, someone unplugged it anyway, might well have been someone else in the office - it wasn't exactly a proper server room)

It was not just that the server crashed, but the ventilation proved to be bad enough that one of the SCSI drives (which should have been in a RAID, but wasn't...) wouldn't start.

They ended up opening it to try to kickstart it manually (been there, done that myself; had a drive survive 6 months with me "helping" the motor spin it up every morning; yes I backed everything up very regularly during that period), finding the drive head had gotten stuck to whatever material covered the plate. They ended up putting the drive in an oven while connected, and heat it until it spun up, and which point they dumped what data they could.

Re: The code worked differently when the moon was full

#119

Earlier quoted context omitted.

You get the same problem with geostationary satellites, e.g. for satellite TV. There's period of about 10 days every spring and fall where, for up to 30 minutes every day, the sun transits 'behind' a satellite within the beamwidth of the dish and totally overwhelms the signal at the LNB.

Once upon a time I had a problem with remote control. It woukd stop working from different positions, but from time to time, not always. It took a while for me to realize there’s a heating radiator behind my back in that directions. And it went hotter or colder depending on thermostate. I guess at one point its IR output would overwhelm IR output from remote control.

When I first read this comment I was picturing a hot water radiator behind you, so it sounded unlikely based on the blackbody radiation curve for ~320 K.

But now I realize you're probably talking about an electric heater. Given that their heating elements get so hot that they're putting out visible red/orange light, it seems very plausible that an electric heater could produce enough ~940 nm IR to drown out the signal from the remote.

Thanks for sharing! I will try to keep this in mind when I'm troubleshooting IR remotes in the future.

Re: The code worked differently when the moon was full

#120
post #71
post #26

We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…

I knew a guy who was a computer tech early in his career. One of his rounds was on a military base, and they had just moved their computer room up one floor. They started having problems with their tape drive, it would just randomly pop up an error while they were using it. He tried mightily to diagnose the problem but couldn't figure it out. Finally he took a break and walked to the nearest window and looked out. He…

I sent my Commodore 64 for repairs more than once only for them to find nothing wrong until we realised it was the buildup of static electricity from being stored under our big TV - it "broke" when we didn't use it for a while but watched lots of TV. It'd be "fixed" by the time it took before the repair people got around to it.

The symptom was that it started "typing" automatically.

Post reply on HN