Great explanation. Also, I always think that if you have really worked on couple of big projects, you don't need to separately prepare for a system design interview. They are pretty straight forward. It's all about following best practices.
Amazing presentation. After watching few videos, my break down of tackling the Frontend System Design's Low-Level Design (i.e. Component Design) would be into three parts: Functional, Non-functional and Components Architecture. Accessibility and Performance would be part of Non-functional requirements. Component architecture would include semantic markup (very important), alongside API and Props.
Great video. Question: is debouncing a functional requirement? Unless not having it causes the app to be unusable, surely this is a non-functional requirement that just increases the overall UX of the app?
in normal System design we try to optimize backend resources like servers, databases. And in Frontend System Design we try to improve our logic such that our Frontend has minimal load and all the UI pages open as quick as possible
That's why i don't like system design round because its more like tic-talk rather than having teching discussion or writing code .. Anyway i know this round is important .. but personally i don't like this round at all...
Miro's FE system design interviews are way more complex than that. They asked me to design a real-time collaboration board 🤯 that's like god-level unless you know well about web sockets and canvas 2D. I used this video to prepare for the interview, and obviously I failed :D
Great session, got so much insights. Would like to have more sessions like this. Specially topics related to frontend system design. Really appreciate your work, you guys are doing great work.
