Scientists spend an increasing amount of time building and using software. However, most scientists are never taught how to do this efficiently. As a result, many are unaware of tools and practices that would allow them to write more reliable and maintainable code with less effort. We describe a set of best practices for scientific software development that have solid foundations in research and experience, and that improve scientists' productivity and the reliability of their software.

@article{wilson2012practices, author = {Wilson, Greg and Aruliah, D. A. and Brown, C. Titus and Hong, Neil P. Chue and Davis, Matt and Guy, Richard T. and Haddock, Steven H. D. and Huff, Katy and Mitchell, Ian M. and Plumbley, Mark and Waugh, Ben and White, Ethan P. and Wilson, Paul}, title = {Best Practices for Scientific Computing}, journal = {CoRR}, year = {2012}, volume = {abs/1210.0530}, url = {http://arxiv.org/abs/1210.0530}, keywords = {science, research, toread}, abstract = {Scientists spend an increasing amount of time building and using software. However, most scientists are never taught how to do this efficiently. As a result, many are unaware of tools and practices that would allow them to write more reliable and maintainable code with less effort. We describe a set of best practices for scientific software development that have solid foundations in research and experience, and that improve scientists' productivity and the reliability of their software.} }

%0 = article %A = Wilson, Greg and Aruliah, D. A. and Brown, C. Titus and Hong, Neil P. Chue and Davis, Matt and Guy, Richard T. and Haddock, Steven H. D. and Huff, Katy and Mitchell, Ian M. and Plumbley, Mark and Waugh, Ben and White, Ethan P. and Wilson, Paul %D = 2012 %T = Best Practices for Scientific Computing %U = http://arxiv.org/abs/1210.0530

Scientists spend an increasing amount of time building and using software. However, most scientists are never taught how to do this efficiently. As a result, many are unaware of tools and practices that would allow them to write more reliable and maintainable code with less effort. We describe a set of best practices for scientific software development that have solid foundations in research and experience, and that improve scientists' productivity and the reliability of their software.

@article{wilson2012practices, author = {Wilson, Greg and Aruliah, D. A. and Brown, C. Titus and Hong, Neil P. Chue and Davis, Matt and Guy, Richard T. and Haddock, Steven H. D. and Huff, Katy and Mitchell, Ian M. and Plumbley, Mark and Waugh, Ben and White, Ethan P. and Wilson, Paul}, title = {Best Practices for Scientific Computing}, journal = {CoRR}, year = {2012}, volume = {abs/1210.0530}, url = {http://arxiv.org/abs/1210.0530}, keywords = {programming, science, computing, research}, abstract = {Scientists spend an increasing amount of time building and using software. However, most scientists are never taught how to do this efficiently. As a result, many are unaware of tools and practices that would allow them to write more reliable and maintainable code with less effort. We describe a set of best practices for scientific software development that have solid foundations in research and experience, and that improve scientists' productivity and the reliability of their software.} }

%0 = article %A = Wilson, Greg and Aruliah, D. A. and Brown, C. Titus and Hong, Neil P. Chue and Davis, Matt and Guy, Richard T. and Haddock, Steven H. D. and Huff, Katy and Mitchell, Ian M. and Plumbley, Mark and Waugh, Ben and White, Ethan P. and Wilson, Paul %D = 2012 %T = Best Practices for Scientific Computing %U = http://arxiv.org/abs/1210.0530