Writing Clean Scientific Software

Nicholas A. Murphy
2020 Zenodo  
This presentation discusses strategies for writing clean scientific software. Choosing meaningful variable names improves readability. Functions should be short, do exactly one thing, and have no side effects. High-level big picture code should be separated from low-level implementation details, for example by writing code as a top-down narrative. Because comments often become out-of-date as code evolves, it is preferable to refactor code to improve readability rather than describe how it
more » ... Well-written tests increase the flexibility of code. This presentation encourages us to think of code as communication.
doi:10.5281/zenodo.3922957 fatcat:ytfrxkswlvewvfs6min6qsadci