Probably not you… or me, or anyone.
BUT – in our current state of code, this is still the BEST tool to control code quality, get other team members to be familiar with your code, and avoid stupid mistakes.
Still – it’s a mystery of how to do it RIGHT. Everyone’s got their own standards for CR and arguments aren’t too scarce to be found.
What can solve this? A firm, clear policy everyone could follow.
Maybe something like this for a start:
Like what you see?
Sign up to our newsletter to get more tips,
best practices and helpful solutions
straight out from our own experience in the Front-end world.
We won’t spam you and won’t sell your email to nobody. Scouts promise!