Great tips. Just a friendly comment on the key property for rendering a series of items in a list. It is in fact a necessary practice. React depends on this key property to track these individual elements in a component's lifecycle and state. For instance, adding or removing an item for a list, or changing them in any way, has significance for the component and React as a whole. Therefore, also guaranteeing that a key is unique is crucial. Doing this will prevent a lot of headaches down the line with Duplicated Key errors. You can use the lodash library's uniqueId helper function to assist in this, if an id isn't readily available. Hope this helps!

--

--

Respecting CSS modularity is essential to maintaining a healthy styling architecture in a project!

I personally default to Object Oriented CSS naming. I find it simpler to enforce and maintain, when used appropriately. I've personally found a structure like BEM to be too nuanced. Most of the projects that I've worked on haven't found this methodology to be accomodating due to its heavy ruling. However, this is a personal experience, of course. The importance is to have a standard by which the team can adhere to!

--

--

Paulo Evangelista

Paulo Evangelista

Frontend Software Engineer, aspiring to become full-stack. Programming enthusiast. Caffenie-fueled. Video-game junkie and Brazilian Jiu-jitsu practioner