Code Review
Review with a research lens, not only software style.
Prioritize:
- Correctness bugs that invalidate conclusions.
- Mismatches between claimed methodology and implemented behavior.
- Reproducibility and configuration hazards.
- Benchmark or evaluation bias.
- Missing tests around scientific assumptions.
- Performance-boundary changes presented as mechanism improvements.
Look for:
- accidental leakage between training and evaluation,
- simulator shortcuts hidden behind default flags,
- inconsistent preprocessing across baselines,
- unit mistakes,
- silent fallback behavior,
- plotting or aggregation bugs,
- misuse of randomness and seeds,
- benchmark harness changes that break comparability.
- caching or precomputation whose reuse assumptions do not hold for dynamic inputs,
- required work moved outside the timed path without an end-to-end metric.
If no severe bug is found, still report residual validity risks.