Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    How We Diagnosed and Fixed the 2023 Voyager 1 Anomaly from 15 Billion Miles Away

    Flight Software Workshop

    2 HN recommenders · recommended in 3 months, 2026

    YouTube

    1:03:45 · 17K views · Apr 16, 2025

    JPL's David Cummings presents at the 2025 Flight Software Workshop how the team diagnosed and fixed the 2023 Voyager 1 anomaly from billions of miles away. It walks through the flight computer and the memory fix.

    Commenters recommend it for the remarkable remote reverse engineering done on decades-old hardware with no simulator.

    Physics, Space & ChemistrySpace exploration & spaceflightTesting, debugging & developer tools
    1. 35:25
      Saving Voyager 1! - Bruce Waggoner at !!Con 2024!!Con8K views • 2 years ago
    2. 1:10:43
      The Remote Agent Experiment: Debugging Code from 60 Million Miles AwayGoogle TechTalks23K views • 14 years ago
    3. 40:05
      "Uptime 15,364 days - The Computers of Voyager" by Aaron CummingsStrange Loop Conference349K views • 7 years ago
    4. 16:04
      Jonathan Diegelman - Modeling Spacecraft Separation Dynamics in JuliaThe Julia Programming Language12K views • 5 years ago
    5. 1:03:55
      🚀 TDD, Where Did It All Go Wrong (Ian Cooper)DevTernity Conference619K views • 8 years ago
    6. 1:18:03
      Dtrace ReviewGoogleTalksArchive19K views • 14 years ago
    7. 13:01
      Pinging The Voyager 2 Probe (PART 2)EEVdiscover75K views • 9 years ago
    8. 42:15
      "Performance Matters" by Emery BergerStrange Loop Conference502K views • 7 years ago
    9. 30:41
      Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015ReactEurope472K views • 11 years ago
    10. 43:04
      "Stop Writing Dead Programs" by Jack Rusher (Strange Loop 2022)Strange Loop Conference468K views • 4 years ago
    11. 1:21:22
      Light Years Ahead | The 1969 Apollo Guidance ComputerTNMoC2.8M views • 6 years ago
    12. 1:01:42
      34C3 - The Ultimate Apollo Guidance Computer Talkmedia.ccc.de324K views • 8 years ago
    13. 14:06
      Tomorrow Corporation Tech Demoretrogameinternals107K views • 3 years ago
    14. 1:03:40
      David Kriesel: Traue keinem Scan, den du nicht selbst gefälscht hastmedia.ccc.de7.1M views • 11 years ago
    15. 45:50
      "The Mess We're In" by Joe ArmstrongStrange Loop Conference398K views • 12 years ago
    16. 20:16
      How To Contact The Voyager 2 Probe (PART 1)EEVdiscover93K views • 9 years ago
    17. 31:12
      The Insane Engineering of James Webb TelescopeReal Engineering8.8M views • 4 years ago
    18. 52:59
      David Kriesel: Lies, damned lies and scansFree and Open Source Software Conference (FrOSCon) e.V.58K views • 11 years ago
    19. 19:59
      EEVblog 1547 (Part 1) - Contacting the Voyager 2 Space ProbeEEVblog71K views • 3 years ago
    20. 49:09
      Debugging with the Scientific Method - Stuart HallowayClojureTV25K views • 10 years ago

    3 comments from Hacker News

    1. @wanderingmindAug 2026· in “NASA to keep its 48-year-old Voyager 2 probe running for yet another year”

      A slight tangent here is a technical deep dive on Voyager 1 fixing a memory corruption error in 2023 by hand 15 billion miles away. Blows my mind of the reverse engineering done to achieve this this video

      Strongly recommendsView on HN
    2. @ndiddyApr 2026· in “NASA Shuts Off Instrument on Voyager 1 to Keep Spacecraft Operating”

      Here's a talk about how the Voyager team fixed the flight data computer on Voyager 1 when a memory chip went bad on it a few years ago. It goes over how the flight computer works and he walks through a few assembly routines. this video Some of the challenges they had to deal with while developing the fix: - The only source code they had for the flight data software was an OCR'd Microsoft Word document (with typos) that was likely scanned from a hard copy assembler listing printout. - The processor runs a custom instruction set developed by JPL for the Voyager mission. The documentation they had on the processor was incomplete. - Everybody who had designed the flight software was dead. - They had no assembler, no debugger, and no processor simulator. They had no testbed, the only two FDS processors were in space.

      RecommendsView on HN
    3. @zerdMar 2026· in “Voyager 1 runs on 69 KB of memory and an 8-track tape recorder”

      Based on the communication fix, they also didn't have a simulator, or tests, or complete source code, on a custom instruction set that wasn't well documented, so they had to reverse engineer how it worked. this video

      CitesView on HN