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

I don't think this is good advice for building, programming, or operating spacecraft.

Edit to add detail: a spacecraft tends to have lot of subsystems that need to work together well, each requires a specialist lead, and there's a high return on investment for things like improving efficiency, sharing resources between subsystems, etc. leading to reduced power, data, and mass requirements. They tend to be bespoke and high value so it's critical that detail knowledge is spread among multiple people, edge cases are carefully considered, and lessons learned get learned by everybody. Collaboration is key in that kind of endeavour. If you're slapping together a CRUD app that can't hurt anyone, sure, go hog wild.



Or medical software. It's great advice for people building products which don't need to work correctly up into the high 9s.




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

Search: