Please enable JavaScript.
Coggle requires JavaScript to display documents.
Code Review - Coggle Diagram
Code Review
Key Areas
Func correctness
Structuaral Correctness
Handles enough edge cases
Could be shorter or faster
Could be safer
Could be replaced with a more effective functional equivalent
Appropriate patterns are used for solving the problem
Redundancies are eliminated
Dependencies introduced by the code change are needed or worthwhile
All other "clean code" principles are followed
Readability
grasp the concepts in a reasonable amount of time
flow is logical
keep track through multiple files or functions
consistent naming
code consistent with the project in terms
code have TODO comments
Test Correcntess
edge cases
readable
consistency
covers all use cases of business logic
Not-functional hidden implications
not have security vulnerabilities
Use of standards and features supported in required systems
Use of libraries with license types that are permitted
Types
Specialist's
Peer
Instant
Checklists
Developer
My code compiles
My code has been developer-tested and includes unit tests.
My code is well-documented.
My code is tidy
I have eliminated unused imports and code editor warnings.
My code follows my team’s established coding standards.
There are no hardcoded, development-only details still in the code.
I considered performance and security.
No code can be replaced with calls to external reusable components or library functions.
Reviewer
Functional Correctness/Business Logic
Structural Correctness/Design
Readability/Complexity
Test Correctness
Non-Functional Hidden Implications