# Questions to Ask

- Does it satisfy the original requirements?
- Is it logically correct?
- Is there no unnecessary complexity?
- Is it robust (i.e., no concurrency issues, proper error handling, etc.)?
- Is it performant?
- Is it secure (i.e., no SQL injections, etc.)?
- Is it observable (i.e., metrics, logging, tracing, etc.)?
- Do newly added dependencies pull their weight? Is their license acceptable?

Learn more from the following resources:

- [@article@Three Pillars of Observability: Logs, Metrics and Traces - IBM](https://www.ibm.com/think/insights/observability-pillars)
- [@article@Security Code Review Checklist - Redwerk](https://redwerk.com/blog/security-code-review-checklist/)
- [@article@What Is Clean Code? - Codacy](https://blog.codacy.com/what-is-clean-code)