On Wednesday, a message sent to Voyager 1 will take a full day to reach it.
The spacecraft launched on September 5, 1977. According to AP's report on Phys.org, it's about to become the first human-made object one light-day from Earth: more than 16 billion miles out, where radio signals need 24 hours to make the trip. EarthSky puts the moment at around 10:16 UTC on November 18, 2026.
I've been writing software for 15+ years, mostly PHP and Symfony, and now I lead a team. My first thought wasn't about space. It was: that's the oldest production system humanity still runs, and its deploy pipeline just got slower.
A 48-hour feedback loop
Think about how we work. Change a line, refresh the page, see the result in a second. If CI takes ten minutes, we complain in Slack.
Voyager's team now works like this:
- Write a command for a 1970s computer.
- Send it. Wait 24 hours for it to arrive.
- Wait another 24 hours for the reply.
- Find out whether you fixed the problem or made it worse, on a machine nobody can ever touch again.
No rollback button, no SSH, no "let me just restart it". In 2024 the team recovered the spacecraft from a failed memory chip by moving code to other parts of memory from billions of miles away. I've seen senior engineers panic over a migration on a server in the same building. I've been that engineer.
Why it still works
I'm not a NASA engineer, so I'll stay humble here. But from the outside, a few things are clear, and they match what I've learned the hard way:
- Simple beats clever. The systems I've seen survive the longest were the boring ones. Fewer moving parts, fewer surprises.
- Change carefully when change is expensive. When every fix costs two days, you think before you type. Most of us never feel that pressure, so we skip the thinking.
- Documentation is a gift to strangers. The people keeping Voyager alive today weren't the ones who built it. Every legacy codebase I inherited taught me the same lesson. The README you skip today is the outage someone else debugs at 2 a.m.
The other side
I don't want to turn this into "all software should be built like Voyager". It shouldn't.
I've built many startups. Several failed, a few worked. None of the failures happened because the code wasn't built to last 49 years. They failed because we were too slow to find out whether anyone wanted the thing. In a startup, a 48-hour feedback loop would kill you long before the bugs did.
So the real skill is knowing which mode you're in. Voyager mode: careful, simple, documented, built to outlive its authors. Startup mode: fast, a bit messy, built to learn. Problems start when a team uses the wrong mode, like startup speed on billing code, or spacecraft-level caution on a landing page experiment.
As a team lead, a lot of my job comes down to asking that question out loud before we start.
A small thing you can do on Tuesday
NASA is running a worldwide celebration called Shine Bright for Voyager's Light-Day. After sunset on Tuesday, November 17, point a phone light or flashlight at the sky and flash V-G-R, the mission's call sign, in Morse code:
- V: short, short, short, long
- G: long, long, short
- R: short, long, short
Short flashes are under a second, long ones about a second. Repeat it for about a minute. If you don't trust your thumbs, NASA has an automatic flasher at go.nasa.gov/vgr (Popular Science has the details).
Voyager won't see it, of course. But a light flashed at the sky for a machine launched before most of us wrote our first line of code feels like the right kind of thank you.
Voyager 2, launched a few weeks earlier, won't reach the same mark until around 2035. A full light-year is about 18,000 years away for Voyager 1. Some deadlines are fine to miss.
Your turn
What's the oldest piece of tech (hardware, software, or that one cron job nobody dares touch) that you still rely on every day? And why do you still trust it?
