Timeline for Programming cleanly when writing scientific code
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2018 at 22:19 | history | edited | Thorbjørn Ravn Andersen | CC BY-SA 4.0 | added 84 characters in body |
| Jul 8, 2018 at 14:53 | comment | added | David Hammen | How has this answer not received an upvote? It has now. Our group has found peer review to be one of the most effective tools of all, a lot more important than unit tests when it come to scientific code. It's easy to make an error when translating a complex set of equations in a scientific journal article to code. Scientists and engineers oftentimes make for extremely poor programmers; peer review can catch architectural uglinesses that make the code hard to maintain / understand / use. | |
| Jul 6, 2018 at 8:42 | history | answered | Thorbjørn Ravn Andersen | CC BY-SA 4.0 |