YouTube¶
Overview¶
YouTube channels provide visual explanations for algorithms, system design, and tooling. Use them to complement reading and implementation—not replace it.
Why This Exists¶
Complex flows (Kafka, DNS, GPU kernels) are easier to grasp with diagrams and animations.
Channel ideas¶
- Computer science: university lecture playlists (verify quality), competitive programming walkthroughs
- System design: whiteboard-style sessions—compare multiple channels for consensus
- Infrastructure: cloud provider channels for service deep dives
- Career: compensation and interview prep—treat numbers as noisy signals
Key Concepts¶
Verify claims
Prefer channels that cite sources and show trade-offs; avoid hype-only content.
Code Examples¶
Pause every 5 minutes -> summarize aloud -> note one question to test with a doc/source
Interview Questions¶
Are YouTube system design videos enough?
They help for narration practice; you still need to draw diagrams yourself and simulate follow-up questions.
Practice Problems¶
- Watch a system design video, then redraw the diagram from memory
- Implement a tiny component mentioned (e.g., rate limiter) over a weekend
Resources¶
- MIT OCW on YouTube
- Conference talks from Strange Loop, QCon, KubeCon (search playlists)