Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://phpc.social/users/Crell/statuses/112405101294734688">Larry Garfield (crell@phpc.social)'s status on Wednesday, 08-May-2024 22:37:57 JST</a><a href="https://phpc.social/@Crell" title="crell@phpc.social"><img src="https://gnusocial.jp/avatar/50888-48-20221219024753.webp" width="48" height="48" alt="Larry Garfield" style="position: absolute; left: 0; top: 0;">Larry Garfield</a></section><article><p>Career goals.  Absolute programming badasses.</p><p><a href="https://phpc.social/tags/NASA" rel="tag">#NASA</a> <a href="https://phpc.social/tags/programming" rel="tag">#programming</a> <a href="https://phpc.social/tags/Voyager" rel="tag">#Voyager</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3058695#notice-6064794">In conversation</a><time datetime="2024-05-08T22:37:57+09:00" title="Wednesday, 08-May-2024 22:37:57 JST">about 7 months ago</time> <span>from <span><a href="https://phpc.social/@Crell/112405101294734688" rel="external" title="Sent from phpc.social via ActivityPub">phpc.social</a></span></span><a href="https://phpc.social/@Crell/112405101294734688">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/2606867">Y'all, the world is sleeping on what NASA just pulled off with Voyager 1.The probe has been sending gibberish science data back to Earth, and scientists feared it was just the probe finally dying.  You know, after working for 50 GODDAMN YEARS and LEAVING THE GODDAMN SOLAR SYSTEM and STILL CHURNING OUT GODDAMN DATA.So they analyzed the gibberish and realized that it was a total readout of EVERYTHING ON THE PROBE.  Data, the programming, hardware specs and status, everything.  They realized that one of the chips was malfunctioning.So what do you do when your probe is 22 billion km away and needs a fix?  Why, you just REPROGRAM THAT ENTIRE GODDAMN THING.  Told it to avoid the bad chip, store the data elsewhere.Sent the new code on April 18th. Got a response on April 20th - yeah, it's so far away that it took that long just to transmit.And the probe is working again.From a programmer's perspective, that may be the most fucking impressive thing I have ever heard.</a></label><br><a href="https://media.phpc.social/media_attachments/files/112/405/084/185/310/780/original/828d5fcf5fb8fb73.png" rel="external">https://media.phpc.social/media_attachments/files/112/405/084/185/310/780/original/828d5fcf5fb8fb73.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Larry Garfield (crell@phpc.social)'s status on Wednesday, 08-May-2024 22:37:57 JST Larry Garfield
Career goals. Absolute programming badasses.
#NASA #programming #Voyager
In conversationabout 7 months ago from phpc.socialpermalink
Attachments
1. Y'all, the world is sleeping on what NASA just pulled off with Voyager 1. The probe has been sending gibberish science data back to Earth, and scientists feared it was just the probe finally dying. You know, after working for 50 GODDAMN YEARS and LEAVING THE GODDAMN SOLAR SYSTEM and STILL CHURNING OUT GODDAMN DATA. So they analyzed the gibberish and realized that it was a total readout of EVERYTHING ON THE PROBE. Data, the programming, hardware specs and status, everything. They realized that one of the chips was malfunctioning. So what do you do when your probe is 22 billion km away and needs a fix? Why, you just REPROGRAM THAT ENTIRE GODDAMN THING. Told it to avoid the bad chip, store the data elsewhere. Sent the new code on April 18th. Got a response on April 20th - yeah, it's so far away that it took that long just to transmit. And the probe is working again. From a programmer's perspective, that may be the most fucking impressive thing I have ever heard.
  https://media.phpc.social/media_attachments/files/112/405/084/185/310/780/original/828d5fcf5fb8fb73.png

Public

Embed Notice

HTML Code

Corresponding Notice