re: 12 Things NOT To Do When Building React Apps With Redux VIEW POST

FULL DISCUSSION
 

In addition to tests I'd also recommend TrackJS, because it catches errors encountered in the wild.

Another thing that I've noticed people to do is to rename a thing, super minimal example:

function Component1({ currency }) {
    return <Component2 money={currency} />
}

function Component2({ money }) {
    return <Component3 price={money} />
}

I think the worst I've had to refactor had three or four different names, while not being the only thing changing it's name as data was passed on.

A third point I've noticed in larger apps is that people seem to develop their own solution each time they can't find something using keywords that pop into their mind. This is one of the reasons naming is important to spend time on. However this is also a communication issue.

 

Those points are right on! Miscommunication should have made it into this list. Miscommunication causes duplicate component implementations because it wasn't visible to the developer at the time. After the issue occurs sometimes we won't have enough time to merge them together because we're being pressured to finish another thing within the end of the day. This causes two separate implementations that practically do the same thing except a tiny change somewhere, like a different named prop for example.

Those of you reading this please make a mental note that communication with your teammates saves time and progress.

code of conduct - report abuse