How do you handle code review in a computational research group?
0 hearts0 comments0 replies
Our group writes a lot of simulation and analysis code, but review practices vary wildly between students and postdocs.
Some share scripts with no comments, others want a full pull-request workflow for every change.
I'm curious how other computational groups set expectations for code review without slowing everyone down.
What has actually worked in your group?