Code checklist
Checklist to adhere to prior to code review
Working notes
- Brief mains
- Good comments + code diary + refer to GitHub issue numbers in comments where applicable
- Subroutines instead of many nested loops
- Complex models obtained from csvs
- Standard macros/programs used
- Followed table guidelines
- Followed programming guidelines
- Understandable variable/file names + follow naming conventions
- Code meets proposal specs
- Results benchmarked against public data (e.g., compare our numbers with Manitoba Health case counts, etc.)
- Asserts/track numbers
- Every stata
capture needs an assert _rc==0 or other way of explicit error handling
- Avoid deeply nested code