Hey everyone,
I recently started a YouTube channel called The Hot Path, where I explain system design, distributed systems, and AI infrastructure concepts with visual animations.
For context, I’ve been working as a backend engineer for 4+ years, and I’m currently a founding engineer at a startup.
While preparing for interviews myself, I realized that I understand system design concepts much better when they are explained visually. Most explanations either stay too high-level or jump straight to the “final architecture” without showing why the design exists, where the naive version breaks, and what tradeoffs actually matter.
That is one of the main reasons I started this channel.
The goal is not to make quick interview-cram videos. I’m trying to explain these topics from first principles:
- Why does this design exist?
- Where does the naive version break?
- What tradeoffs matter in production?
- What do most explanations usually skip?
So far, I’ve published videos on:
- Consistent Hashing
- Rate Limiting
- Load Balancing
- Vector Databases
- Embeddings
Next up, I’m working on a deep dive into RAG end-to-end: chunking, retrieval, reranking, context packing, and why citations are not the same as grounding.
I’m still very early and would genuinely appreciate feedback from engineers here:
- Is the explanation clear?
- Are the visuals useful?
- Are the topics in the right direction?
- What system design / AI infra topics would you want explained this way?
If this feels relevant to you, and if the content resonates with how you learn, please do subscribe and support.
Top comments (0)