The Voyager knowledge-crisis is real but misframed: the threat is fragmented institutional memory and scarce assembly programmers, not unreadable code.
Key Takeaways
Voyager onboard software is assembly language for custom GE interrupt-driven processors, not Fortran; Fortran is tied to ground-side tooling.
Total onboard memory across all three computer subsystems is roughly 64-70 KB; JPL compares operations to flying an Apple II.
The “engineers in their 80s” framing is nine years stale; Larry Zottarelli retired in 2016 and succession has already happened more than once.
The real gap: original paper documentation was lost across office moves, leaving the current team doing archaeology to recover 1970s-80s records.
Hardware decline is the hard deadline: RTGs lose ~4W/year, science instruments are being switched off, and DSN contact may end around 2036.
Hacker News Comment Review
Commenters push back on the career-risk framing NASA cited; working on Voyager is seen as a rare chance to own a full hardware-software stack with a defined endpoint.
The thread treats Voyager as a live case study in mission-critical resilience: complete top-to-bottom stack comprehension at 64 KB scale is viewed as a valuable learning environment, not a dead end.
