Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
a-dub
on Dec 23, 2018
|
parent
|
context
|
favorite
| on:
Simple rules for documenting scientific software
11) Invariant: Someone should be able to go from a referenced paper or book to your code without scratching their head too much. This can be approached by either fortifying the documentation in the code or by specificity in a methods paper.
Consider applying for YC's Summer 2026 batch! Applications are open till May 4
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: