Live data from Hacker News

We found an undocumented bug in the Apollo 11 guidance computer code

juxt.pro

191–200 of 213 posts

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#191
post #181
post #168

Earlier quoted context omitted.

I'm having a really bad Mandala effect right now where I remember some XKCD that wrote a poem about this. Maybe I'm thinking of another comic.

Oh, it's Mandala effect now? I could swear it was Mandela before.

I think it was Madnela?

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#192
post #136

Earlier quoted context omitted.

It's a miracle nobody died in flight during the program. Exploding oxygen tank, rockets shaking themselves to pieces during launch, getting hit by lightning on top of a flying skyscraper full of kerosene and liquid oxygen....

Gus Grissom, Ed White, and Roger Chaffee died on the Apollo program. I feel it's not polite to ignore that fact even if you add an 'in flight' qualifier.

And it's even more interesting in the fact that our rocket program started with the former rocket scientists from Nazi Germany who were brought over at the end of WW2 to work in the American rocket/missile program.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#193

Mike Stewart here! I led the restoration of the AGC documented on CuriousMarc's channel and co-administrate VirtualAGC. There is a lot to unpack here. First: this is indeed a real bug in the AGC software. However, it did not go unnoticed for the whole program. It was discovered during level 3 testing of SATANCHE, and late development branch of the Command Module software COMANCHE. It was assigned anomaly number L-1D-…

The front page has moved on but this is pure gold, thanks for making the time to share all these details.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#195

Mike Stewart here! I led the restoration of the AGC documented on CuriousMarc's channel and co-administrate VirtualAGC. There is a lot to unpack here. First: this is indeed a real bug in the AGC software. However, it did not go unnoticed for the whole program. It was discovered during level 3 testing of SATANCHE, and late development branch of the Command Module software COMANCHE. It was assigned anomaly number L-1D-…

I was hoping you'd comment here. Thank you. Amazing bits of lore.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#196

Software that ran on 4KB of memory and got humans to the moon still has undiscovered bugs in it. That says something about the complexity hiding in even the smallest codebases.

Also contrast with the busy beaver problem and how much can be done with a small handful of instructions.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#198
post #174

Earlier quoted context omitted.

While I agree with the sentiment, using AI to write the final draft of the article isn’t cheating. People may not like it, but it’s more a stylistic preference.

Using AI and a human byline is 100% cheating.

Yeah I agree. Don't tell me you authored something when claude did the majority of the writing. Use claude if you want, but don't pretend you wrote the content when you didn't.

I also hate this style of plastic, pre-digested prose. Its soulless and uninteresting. Maybe I've just read too much AI slop. I associate this writing style with low quality, uninteresting junk.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#199
post #23
post #2

Super interesting. I wish this article wasn’t written by an LLM though. It feels soulless and plastic.

This is the top reply on a substantial percentage of HN posts now and we should discourage it. It is: - sneering - a shallow dismissal (please address the content) - curmudgeonly - a tangential annoyance All things explicitly discouraged in the site guidelines. [1] Downvoting is the tool for items that you think don't belong on the front page. We don't need the same comment on every single article. [1] - https://news…

The guidelines you linked says this:

> Don't post generated comments or AI-edited comments. HN is for conversation between humans.

The same principle applies to submissions. If you couldn't be bothered to write it, don't ask me to read it. HN is for humans.

Re: We found an undocumented bug in the Apollo 11 guidance computer code

#200
post #84

Earlier quoted context omitted.

You're suggesting this is the complainant's fault?

Yes. These HN guidlines already basically cover it: > Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. > Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.

Its not a person's work. It reads like an LLM's work. If you can't be bothered to write an article yourself, its incredibly arrogant to ask me to read it.

Speaking of the HN guidelines, they also say this:

> Don't post generated comments or AI-edited comments. HN is for conversation between humans.

Post reply on HN