HackerTubewatch
Surprise me
Frame from CNN, Feynman and the Challenger disaster Plays via YouTube's privacy-enhanced embed

CNN, Feynman and the Challenger disaster

vsrr83
Interviews
YouTube
1 HN user recommended this interview1 month2016–2025 score 1
Years with an HN recommendation, 2007–2026

HN cites it for Feynman's insights on NASA risk reasoning, blame and engineering culture, and the contrast between Apollo and the Shuttle.

A June 1986 CNN interview with physicist Richard Feynman about the Challenger disaster and the management failures he found while serving on the investigating commission.

“Richard Feynman served on the Challenger commission and very nicely summarizes the difference between Apollo and Space Shuttle.” (HN, 2025)

1 recommendations · 3 citations · Interviews

4 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@prasadjoglekar Aug 2025 Recommends
on HN thread Starship's Tenth Flight Test
It was reusable, but way over promised. Don't take my word for it. Richard Feynman served on the Challenger commission and very nicely summarizes the difference between Apollo and Space Shuttle. [this video] SpaceX is doing stuff that's just beyond the scope of what's deemed conventionally realistic. That's achievable and pushes us forward.
Feynman summarizes difference between Apollo and Space Shuttle.

Citations, criticism and jokes

@pdkl95 Feb 2016 Cites it
on HN thread Unsafe Lead Levels in Tap Water Not Limited to Flint
> the absence of known danger is not the same as safety. Feynman had some interesting comments on this problem regarding NASA's "it worked ok last time" approach to risk assessment before the Challenger Disaster. [this video]
Feynman on NASA's it-worked-last-time risk reasoning.
@pdkl95 Jul 2017 Cites it
on HN thread A hacker stole $31M of Ether – how it happened, and what it means for Ethereum
Read more
> the model of 'public by default, opt in for security' is fundamentally daft in this context. It's daft in most contexts, and is one of the largest sources of security problems. If your design requires enumerating badness [1], you're doing it wrong. > from: [link] >> Just about every ICO, trust and company used the Parity multisig wallet, and that code was considered well-tested. -sigh- This is, unfortunately, a common problem. "It worked ok the last N times" and "It passed a lot of tests" do not mean it's bug-free and safe to use. Richard Feynman was right during the Challenger investigation when he called this a childish attitude . (He was also right in not wanting to assign blame, instead asking "How do we educate the child?"[2]) [1] [link] [2] [this video]
Feynman on blame and educating the child.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close