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

but the hip programming tips these days are to move fast and break things!

a rocket certainly moves fast...



It's not like SpaceX didn't break things either: https://www.youtube.com/watch?v=bvim4rsNHkQ.

The real trick is knowing when it's OK to break things in experimentation and the acquisition of knowledge, and when everything needs to run smoothly.


It would have broken a bunch of things if it weren't "about 328 feet" off target, too.

When they said they lost the core, I've been envisioning a barge with a big, round hole in the center...


They intentionally aim off-target, and have the final engine burn steer them back into the landing.

If an engine relight doesn't happen, they won't hit the barge.

I think the biggest danger to the barge is a final engine relight without enough fuel, or with a guidance and nav systems failure or error.


-OT, but related - for the same reason, offshore vessels set their autopilot targets say, half a mile off the oil rig/whatever they are headed for - just in case someone doesn't pay attention as they approach.

I once saw a nice enamelled sign on a bridge stating 'Whoever programs a target on target will be promoted to figurehead prior to arrival at said target.'

(And, in that position, being the first to regret their sloppiness. Plus, they will somewhat soften the impact. Cough.)


Super interesting. Something I wouldn't have ever thought about, but makes perfect sense.

The world is just frighteningly complex, sometimes.


SpaceX have been moving fast and breaking things. It's worked out pretty well for them, even in non-software.




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

Search: