HackerTube
HomeLongsLikedHistoryWatch laterCategoriesPlaylistsSettings

code structure

Explainer×Hidden gems×Play all on YouTube

Upload date

Past year2020s2010s2000s

Type

TalkLectureExplainerTutorialDocumentaryInterviewDemoCommentaryComedyMusic

Duration

Under 4 minutes4-20 minutes20-60 minutesOver 1 hour

Features

Hidden gemsEvergreen only

Sort by

RelevanceRecently recommendedUpload dateOldest firstView countLike ratioMost recommended
Who else benefits from the Dutch cycling infrastructure4:01

Who else benefits from the Dutch cycling infrastructure

88K views • 13 years ago
BicycleDutch
A short BicycleDutch episode showing how people with disabilities use Dutch cycle tracks on hand-cycles, tricycles and mobility scooters.
AI Learns Noise Filtering For Photorealistic Videos | Two Minute Papers #2154:17

AI Learns Noise Filtering For Photorealistic Videos | Two Minute Papers #215

65K views • 8 years ago
Two Minute Papers
A Two Minute Papers episode on NVIDIA's recurrent denoising autoencoder, which cleans up noisy Monte Carlo path-traced image sequences. It shows how a neural network can produce usable renders from very few samples.
Orbital Data Centers Yes or No14:32

Orbital Data Centers Yes or No

18K views • 1 year ago
Eager Space
Eager Space examines the practicality of putting data centers in orbit, walking through three scenarios with cost calculations and the launch cost reductions that would be required.
Topic match · Cloud, DevOps & reliability
Dutch junction design - safer for cyclists4:01

Dutch junction design - safer for cyclists

52K views • 15 years ago
BicycleDutch
A short BicycleDutch episode showing how Dutch junctions with protected cycle paths are laid out. It argues these are proven, non-experimental designs that make intersections safer for cyclists.
Debt Metaphor4:44

Debt Metaphor

95K views • 17 years ago
Ward Cunningham
Ward Cunningham explains the history and intent of the debt metaphor, which he coined while refactoring the WyCash product. He says debt means code reflecting an incomplete understanding of the problem, not sloppy programming.