Hacker News new | past | comments | ask | show | jobs | submit | waz0wski's favorites login

Initially posted this as a reply, but going top-level, cause the hot takes are too spicy for my liking.

So the plan was to test x, y, and z. Launch sequence and takeoff, stage separation and Starship engine light, and the post-launch stuff like booster wet landing, reentry, and heat tiles. The booster by itself is not aerodynamic, so the only way to test x is with a starship on top. And if you have starship, you might as well test y and z. But it's not a primary goal. Any more effort in polishing y and z is "premature optimization". X was the test. SpaceX did the X, we got max Q.

On the most recent SmarterEveryDay video on encasing a Prince Rupert's drop in glass, sculptor Cal Breed talks about the moment when a process fails. He could stop there and restart, saving some time, but instead all the pressure is off, and he "makes as many mistakes as possible" for the rest of the build. Quote is towards the end, but the whole vid is worth a watch.

https://youtu.be/C1KT8PS6Zs4

https://www.calbreed.com/

Edit: also, they needed the flight plan all the way through "total success" in order to file with the FAA. You can't just have "oh sweet, 100% of booster things worked, we now have a suborbital craft careening on a parabolic trajectory". I didn't read a flight plan, but I imagine they must have spelled out each possible outcome exhaustively.


Consider applying for YC's W25 batch! Applications are open till Nov 12.

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

Search: