this post was submitted on 01 Aug 2023
17 points (100.0% liked)

Science

13007 readers
60 users here now

Subscribe to see new publications and popular science coverage of current research on your homepage


founded 5 years ago
MODERATORS
top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago

I find it stressful enough doing an update on a remote server (where there's someone in support who can reboot the box if it all goes wrong). It's got to be something else to send commands to a spacecraft that's now light hours away. It's not just that you can't exactly go out and troubleshoot the hardware, it's also that the ping time is rather extreme so you won't know for hours if you've screwed up or not!

[–] [email protected] 4 points 1 year ago

Voyager 2 is programmed to reset its orientation multiple times each year to keep its antenna pointing at Earth. The next reset is due on 15 October, which Nasa says "should enable communication to resume".

[–] [email protected] 2 points 1 year ago

You have to appreciate the resilience of the design, though, it says the probe has an automatic reset every few months so it will hopefully recover in October when the next reset occurs

[–] [email protected] 1 points 1 year ago (2 children)

Who hasn't pushed bad code to production?

[–] [email protected] 2 points 1 year ago

Imagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe

[–] [email protected] 1 points 1 year ago (1 children)

I've never pushed bad code to production. None of my unit tests fail*.

* I don't ever write unit tests

[–] [email protected] 1 points 1 year ago

We don't do that here

[–] [email protected] -4 points 1 year ago

If the probe is finally dead i.e. we can no longer communicate with it, I feel like it would be a fittingly ignoble end.