- React Digest
- Posts
- Why most design systems implode
Why most design systems implode
#359 – June 06, 2022
sponsor
A good form can be a thing of beauty - and beauty's in the details. Read this blog for everything you need to know about designing & building sleek, user-friendly and accessible Forms.
this week's favorite
This post shares Brad’s design system pitfalls from seven years of experience teaching Atomic Design to folks at Nike, Techcrunch, Time magazine and more. We’ll dig into what does and doesn’t work.
A monorepo is a project which contains smaller projects – whereas each project can be anything from individual application to reusable package (e.g. functions, components). The practice of combining projects dates back to the early 2000 when it was called a shared codebase.
Component in React are the building blocks of an application. They are reusable code blocks that can be used to build pieces of the UI instead of putting everything under one single file. Also, a component can have other aspects such as states, props, etc.
Throttle and Debounce solve optimization problems. Throttle skips function calls with a certain frequency. Debounce delays a function call until a certain amount of time has passed since the last call.
We often have a requirement to show a large amount of data on the screen. The conventional approach is to map through the data & return the JSX. Everything goes into the DOM and gets rendered. But if the list is too big, it's costly and will result in slow load time & a sluggish interface. Let me explain this with an example.