- If during the review, code "around" the implementation can be improved, decide with the author whether a separate engineering task should be created or if it can be part of the current PR. Usually opt for the first option.

- Open touched files in the IDE and check for ESLint/Prettier/TypeScript warnings and errors (pre-commit hooks should already catch these, but ```--no-verify``` exists)
- Test the feature locally and report any bugs that are identified
- Go over the implementation and suggest improvements

- Read the PR's description and request more information if context is missing
- Go through the changes once to check for typos in variable names or comments
- Clone the branch locally

- Make sure the branch name follows the guidelines set by the team/project/company
- Verify commits have meaningful names and are separated pragmatically. If commits will be squashed, check the squash commit message
- Check the PR's target branch

- Don't try to refactor and add functionality at the same time
- A test is the first user of your code
- Create a project glossary

Yours?

- Take small steps always. Check for feedback and adjust before proceeding
- Feedback: anything that independently confirms or disproves your actions
- Design your code to be replaceable
- Don't let existing code dictate future code

- Learn the terminal and automate it
- Use keyboard shortcuts
- Keep all your configurations in plain text files (YAMLs, etc.)
- It's much easier to find and diagnose the problem by crashing early, at the site of the problem
- Code defensively
- Leave assertions in code on

- Learn a new language every year
- DRY: Every piece of knowledge must have a single, unambiguous, authoritative representation within a system
- Orthogonal system: Moving a button on a UI should not require a change in the database schema
- Keep track of your estimates to see how close you were

- Fix bad designs, wrong decisions, and poor code when you see them
- You can't force change in people. Lead by example and encourage them to join
- Only look ahead as far as you can see
- Build software that is easier to change
- Collect, organize, and maintain knowledge