Great video Chirag . Learnt a lot in terms of the requirement gathering phase . Just to make this game a game of skill and not based on luck, one player will have 2 coins to play with. On rolling the dice, he could move either of the two coins based on the snakes and ladders location .
You can do it, but that will impact performance. Consider if I have time based randomly changing snake and ladder position, you have to rerender entire game.
Great video chirag, just one thing that could perhaps be added is the state structure also specifying which component will hold which part of the state
What a great video. Got a glimpse into system design from frontend perspective. Efforts highly appreciated. :) Any blogs or article recommendations to learn about design in depth ?
Really great System Design Series. I have recommended it to all of my friends. Thanks to this series I was able to crack System Design round in Atlassian ❤️🙌🏻. Thank you for sharing your knowledge. Also, I’m bit curious which tool do you use for this presentation 😅
Great to hear that. Will be looking forward for support to spread it with bigger communities, so that more folks can benefit from it. Thanks in advance!
Do we list all the points that we will be covering in the design upfront or we only mention them once we are actually explaining them? By points I mean - component architecture, api design, performance, optimisations, accessibility, security, etc.
Nice explanation. I have some queries. Why do we need to have `addSnake` / `addLadder`(hasSnake) inside Snake/Ladder Interface. Isn't the responsibility of Board/Game interface? Edit: Ok. After watching the component design I can understand why you've kept it outside. You're abstracting it and kept it outside.
