Summary
Most junior engineers can write code. Few can confidently sketch how a real system fits together. The skill that separates the two is called system design, and it is the kind of thing engineers usually only pick up after years of on-the-job exposure to messy production systems. The result is a wide and unnecessary gap between what bootcamps and CS programs teach and what teams actually expect.
This first lesson lays out the case for closing that gap intentionally. Kay introduces himself as a UC Berkeley lecturer and engineering manager with 15+ years of industry experience, and explains why he built this course: junior engineers already have the hardest skill (the ability to write code), but they are stuck because no one has taught them the lens that turns code into architecture. The rest of the course is the framework that lens is built on.
By the end of the seven lessons, you will be able to look at any application — Instagram, Netflix, Uber, Stripe — and see the same handful of building blocks underneath, instead of an impenetrable wall of "real engineering."
Key takeaways
- System design is treated as a tribal-knowledge skill, but it can be taught intentionally with the right framework.
- Junior engineers are not missing intelligence — they are missing a lens that turns code into architecture.
- The framework in this course transfers across stacks and across decades because it sits above any specific technology.
- The end goal is end-to-end intuition: looking at a system and seeing its shape, not just the code in front of you.
You already have the hardest skill in software, which is the ability to write code. What is missing is the lens to see how the code fits together.