react-atomic-design VS system-design-primer

https://github.com/danilowoz/react-atomic-design maybe this as an example

Once I started learning about software development best practices such as the SOLID principles, Atomic Design, abstraction and design patterns my first instinct when writing any piece of new code was to write beautiful code from the very beginning. I wanted to make sure that my code was readable, maintainable, and scalable. However, I quickly realized that this approach was not only time-consuming but also led to frustration. I was spending too much time trying to make my code look perfect, and not enough time focusing on getting the job done. This got worse when I started working on larger projects with more complex code and TypeScript, where typing can be a bit tedious for reusable components.

2. React Atomic Design

React's biggest selling point is _declarative composability_. If you want to split functionality into other components, _just make other components_. It is common (and probably best) practice to design components [atomically](https://danilowoz.com/blog/atomic-design-with-react). If you need to share state between them, _hoist that state to a common ancestor_ component and pass it down through props. If you need props from a much more general location, you can look at using contexts, although be careful about this as they have some significant drawbacks.

I feel like this frees you up to use things like Atomic design with your components, which helps on the more folder-structure side of things.

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx