Deliverable_3.md

@@ -747,6 +747,58 @@ As Campus Chris, I want to create a list that contains my favourite recipes.
 | **Implementation** | Do loops/branches terminate correctly? | Yes |
 | **Implementation** | Are if-else/switch structures complete and readable? | Yes |
 
+## **Aron – Code Review for Hooriya**
+
+| Category | Inspection Question | Answer |
+|----------|---------------------|--------|
+| **General** | Does the code work as intended for the feature being reviewed (e.g., search, filters, comments, recipe upload, leaderboard)? | Yea |
+| **General** | Is the code easy to read and understand without relying on external explanations? | Yea |
+| **General** | Does the code follow our team’s conventions (React component naming, consistent indentation, meaningful variable names, clear folder structure)? | Yea |
+| **General** | Is there any repeated logic that could be moved into shared utilities (e.g., API error handlers, database queries, form validation)? | Nah |
+| **General** | Is the component or function modular, or is it doing more than one responsibility? | Modular |
+| **General** | Are there unnecessary global variables or shared state values? | Nah |
+| **General** | Is there commented-out code that should be removed? | Yea |
+| **General** | Are loops, array maps, and async workflows properly controlled? | Yea |
+| **General** | Do variable and function names clearly describe their purpose? | Yea |
+
+| **Performance** | Are there any expensive operations running too often (re-fetches, un-memoized computations)? | Nah |
+| **Performance** | Can built-in methods replace custom loops? | Nah |
+| **Performance** | Are unnecessary console logs/debugging statements left in the code? | Yea |
+| **Performance** | Are API calls grouped efficiently? | Yea |
+
+| **Security** | Are backend inputs validated before being used in queries? | Yea |
+| **Security** | Are database queries protected using parameterized queries (pg-pool)? | Yea |
+| **Security** | Are errors from third-party tools handled properly? | Yea |
+| **Security** | Are invalid parameters rejected with proper error responses? | Yea |
+| **Security** | Are protected routes using authentication middleware correctly? | Yea |
+
+| **Documentation** | Are comments meaningful where logic is not obvious? | Yea |
+| **Documentation** | Are all API routes documented clearly? | Yea |
+| **Documentation** | Are edge cases explained? | Yea |
+| **Documentation** | Are third-party libraries used clearly? | Yea |
+| **Documentation** | Are TODOs marked clearly? | Yea |
+| **Documentation** | Are data structures explained? | Yea |
+
+| **Testing** | Is the code structured to be testable? | Yea |
+| **Testing** | Can functions be manually triggered for testing? | Yea |
+| **Testing** | Are input validations testable? | Yea |
+| **Testing** | Could custom logic be replaced with built-in utilities? | Nah |
+
+| **Implementation** | Are descriptive variable names used consistently? | Yea |
+| **Implementation** | Any confusing or similar variable names? | Nah |
+| **Implementation** | Are state/backend variables initialized properly? | Yea |
+| **Implementation** | Should non-local variables be moved inside functions? | Nah |
+| **Implementation** | Should literal values (rating limits, pagination size) be constants? | Nah |
+| **Implementation** | Are constants used for repetitive values? | Nah |
+| **Implementation** | Are function/handler names descriptive? | Yea |
+| **Implementation** | Are parameters validated before use? | Yea |
+| **Implementation** | Do functions return correct structures/status codes? | Yea |
+| **Implementation** | Any overflow or invalid calculation risks? | Nah |
+| **Implementation** | Are parentheses/grouping used correctly? | Yea |
+| **Implementation** | Are async operations handled safely? | Yea |
+| **Implementation** | Do loops/branches terminate correctly? | Yea |
+| **Implementation** | Are conditionals readable and complete? | Yea |
+
 
 **_Hooriya's Report to Aron_**