Speaker
Description
Software engineers, including those involved in scientific software, often mention that they follow best practices. While sounding like an excellent idea, this is often near impossible. Frequently, there is an opinion on what is the best practice. Some other things, like software licenses and naming conventions, are mostly left to the development team to decide. Our software team has developed preferred practices which are guided by best practices rather than constrained by them. These practices reflect the values and realities of the environments and users of our software. To share these decisions with the team, we created a project template. The project template promotes standardization and enables discussion of how various decisions are implemented. This paper will discuss what information belongs in a project template and the benefits of collecting preferred practices in this way.
| Abstract publication | I agree that the abstract will be published on the web site |
|---|
