Software Code Review -
i need code review group's project , have code review on group project. have never done code review, guys know can find example know has in it?
there no 1 way. work, use crucible. amounts commenting on code. things out for:
- ensure code meets standards (set department perhaps)
- proper formatting
- syntax errors (these worst - person must, @ least, have compiled code)
- logical errors (actual errors in logical flow of code)
- risky/fragile/error-prone code
- code hard maintain
- software antipatterns
- bad practices/code smells
- improper naming of variables/methods (self-documenting code important; make sure name methods , variables properly)
- race conditions (in multithreaded code)
- buffer overflows
- infinite recursion
- edge cases have not been handled
there many more; things "don't right". when performing code review:
- criticize code, not person.
- don't combative or brusque instead of saying *"you should doing x, y, z! you're doing (a, b, c) not right!" try saying "why don't try doing x, y, z? a, b, c doesn't right here". posing question makes less aggressive/combative.
- a code review supposed educational experience. aim other person learn mistakes (if any); code review great place knowledge transfer.
Comments
Post a Comment