As for coding standards, I recommend them for readability of the code. And they should be applied prior to the peer-review, it levels the code base for the different experience levels on a team.
The coding standards should be living so it can improve/evolve with the team, tools, technology and language. And have one per language used.
I believe a coding standards should be local to a team, not something dictated on a company level. Standards should be open so they can borrow/inspire others, but teams, product, languages and problems can vary.
As for the checklist, “security” should be there, humans are good at spotting security issues. Supported by tools and tests of course, just lige the other aspects of the SDLC.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Really good article on code reviews.
As for coding standards, I recommend them for readability of the code. And they should be applied prior to the peer-review, it levels the code base for the different experience levels on a team.
The coding standards should be living so it can improve/evolve with the team, tools, technology and language. And have one per language used.
I believe a coding standards should be local to a team, not something dictated on a company level. Standards should be open so they can borrow/inspire others, but teams, product, languages and problems can vary.
As for the checklist, “security” should be there, humans are good at spotting security issues. Supported by tools and tests of course, just lige the other aspects of the SDLC.