react-atomic-design VS nodebestpractices

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.

Repository: goldbergyoni/nodebestpractices

ah, but there is one more reason to return await. have a read.

View on GitHub

Flat structure: check out the structure recommended by node best practices, and check out how Nest.js does the structure. The more layers you add, the more complex navigation with the flat structure becomes. With the component structure, it stays easy to use no matter how many components and layers you have.

I am looking for a resource like https://github.com/goldbergyoni/nodebestpractices. I know Sql but I want to learn best practices. Can you recommend me resources for this?

Also, while learning nodejs + express, have a read on the best practices here.

Assuming you have fundamentals in place this repo of best practices can help line things up and link you to areas where you need improvement. https://github.com/goldbergyoni/nodebestpractices

Please don't call node.js single-threaded as this is not true and is annoying. To take advantage of CPUs, this could help.