I learned system design the slow way.
Thick books. Long engineering blogs. Whiteboard sessions where I drew boxes and arrows and hoped they made sense. It worked, eventually. But it took far longer than it should have, mostly because I spent most of that time reading about systems instead of designing them.
Over the last year I've had to learn a lot of new material: vector databases, LLM serving, RAG pipelines, agent architectures. This time I did it differently. I used AI.
Not to do the learning for me. To make the learning faster.
Here's the exact approach, and the one rule that makes it work.
The Problem With How Most People Learn System Design
Most engineers learn system design passively.
They read about consistent hashing. They watch a video on Kafka. They study a reference design of Twitter. Then they walk into an interview, the interviewer says "design a ride-sharing app," and their mind goes blank.
Why?…