Why did I join the course? (ordered randomly) - Simple -
Depth
Knowing what I don't know about ("You don't know what you don't know")
Knowing you, philosophies, the network, everything.
This cohort gives you all.
The best is the idea of evolution with each design. Choose x (all good? yes. - Nope), "what's wrong with this ", tradeoffs?, how to make it better to reach y, ...
I have incorporated this in my notes, in my thinking pattern, everywhere. This is how we should think, actually (makes thinking easier too). You have structured the course so well! All the dabbas are easy to understand - now one can reason about things.
By the 7th week itself, the main designs are just a reference of week 3, week 4, and copy and paste. It's drilled down! That's actually the best part now that I reflect, pre-requisites, and building on older ideas to teach new ones, thereby ensuring people have to recall stuff, spaced repetition.
Apart from this, the times when you repeat things just to drill things into our heads - make it hard to forget XD. Actually, this is one aspect that made me feel that you're a good good teacher. Of course, 50k is no joke, but frankly, this is really 1000x better than any college course or any other teaching material.
The fact that you improve your critical thinking, the discipline this has instilled, every weekend, 7 am at the table, studying, reviewing notes, for learning! (saying no to house parties, because well, sessions are expensive XD)
I'm pretty sure now I'll think around the code aspect, train myself on thinking implementation (even with AI around) because that (as you have shown) brings out the actual issues that require an engineer's mind. Lastly, every morning 15 mins early, to catch up with you, just chit-chatting is so much fun.. Always get to learn new things from you, be it technical, industry or life XD
Generally, after this, I keep on rambling the whole day to my wife, what I discussed with you, what you do, how you are interviewing etc. I'll miss that after the course, OF COURSE.
You are the Rancho of software engineering :P
But in all seriousness, thanks for everything, Arpit. In 8 weeks, you have given everything that is required for any engineer taking this course to succeed, that's all we can ask for.
This course covers enough depth that if you stay attentive throughout, it equips you with everything required to succeed — whether you're a SDE-2 or Staff-level Engineer.
What sets Arpit apart is how he trains you to think. System Design has always been about tradeoffs, understanding the product, and requirements. He forces you to approach problems from all these angles — Business > Product > Engineering.
The idea of evolution in every design is what I found most valuable. You start with the simplest approach, identify its tradeoffs, iterate toward a better solution, and keep going. This way of reasoning is now part of how I think about systems, and it applies well beyond interviews.
The course structure deserves special mention. Concepts build on each other methodically. By week 7, the advanced designs are essentially compositions of building blocks from earlier weeks. Pre-requisites are covered first, then layered upon, which naturally forces recall and reinforces retention.
It also builds critical thinking and discipline. Every weekend, dedicated hours, reviewing notes, going deeper, because the material demands and rewards that level of engagement.
Having explored various learning resources over the years: university courses, books, online content, I can say with confidence that this is significantly more effective than anything else I've come across.
You don't just learn system design. You learn how to think about it.