vercel[bot]
commented
3 weeks ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| gibberle | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 28, 2024 1:38am |
About this PR
57
How to review
Ensure that the mobile and regular navbar appear with the navbar being at the top right and the heading beneath the navbar Check that this remains consistent across different pages
Checklist
Scan your source code for useless code, comments, etc.
Assess whether methods and classes follow single use/responsibility.
There is almost always, no need for duplicated code.
Strive to be concise, write readable code with code style in mind.
Dense or complicated code is documented. Teach it to yourself.
Exceptions are handled and communicated properly (catch block, throw exception, descriptive logs)
Justify if a class/method is as many LOC (lines of code) as it needs to be.
Gauge the validity of your types, use dynamic/complex types as needed.
Scope of access should be as restrictive as possible.
Follow OOP, break big problems into smaller, simpler ones. Design methods/classes with this in mind.
You are the last line of defense.