Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are two good lessons here:

1) Robust system design involves identifying the parts of your system that are mission-critical and always monitoring them. NASA missions have great automation and a 24/7-staffed mission control.

2) If a system failure can result in massive secondary damage, isolate that system. Warehouses receiving orbital payloads should probably be nice and far away from the base you care about.




> Warehouses receiving orbital payloads should probably be nice and far away from the base you care about.

As mentioned elsewhere in the thread, shades of 'The Moon is a Harsh Mistress' by Heinlein.

All your base are belong to dust.


Sorry, having never read that story (nor played Factorio since it went interplanetary) I don't understand the reference.


> 1) Robust system design involves identifying the parts of your system that are mission-critical and always monitoring them. NASA missions have great automation and a 24/7-staffed mission control.

You should alert on critical parts but you should monitor anything and everything you can. It might be critical in finding out why system broke later on. Easier said than done for hardware but easy for software




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: