URGENT!! System Design Interview Prepration
I have an interview in an hour found some insight via leetcode discuss
A friend shared insights from the frontend system design round. The task was to design a dynamic sprint dashboard where users could modify the dashboard by adding columns such as “Backlog,” “Scheduled,” “In Progress,” etc. Each column could contain entities like tasks or stories. The key areas of focus were: Reusable UI Components: The UI components, such as tasks or stories, should be reusable. For example, a Task should be rendered using the same UI component each time. Versioning: Instead of modifying existing UI components, the idea of creating a new version of the component, similar to versioning in backend systems (e.g., Maven), was emphasized.Could someone provide insight for the versioning thing
1 Reply
Sorry to be late on this, but if components should be versioned, my immediate idea would be to extract them to separate package (it could still be in the same repo, by using monorepo structure).
It's hard to provide more insight as there is no clear clue on how this versioning should impact app development.