Tool
Code Reviews
Collaborative practice of reviewing changes before merge; reinforces quality, spreads knowledge and surfaces risks the author missed.
Key points
- ▸Small, focused PRs get faster and better reviews than giant diffs; splitting costs less than the delay it prevents.
- ▸Feedback on the code, not on the person; ask before demanding, propose alternatives when objecting.
- ▸Practical checklist: tests cover the change, errors handled, secrets excluded, docs updated, perf considered.
Seed content from the CV; pending manual review or Trilium ingestion.