Documentation as Infrastructure
Description
Scientific software often fails not because of algorithms, performance, or infrastructure, but because teams cannot sustain the knowledge required to maintain it. As research groups grow and rotate, documentation becomes fragmented, outdated, or entirely absent—creating onboarding friction, duplicated effort, and long‑term maintenance risk. At Purdue University’s Rosen Center for Advanced Computing (RCAC), I have worked across multiple research software and training projects to design and implement a centralized documentation strategy that treats documentation as shared infrastructure rather than a side task.
Notes
Files
Documentation as Infrastructure.pdf
Files
(225.8 kB)
| Name | Size | Download all |
|---|---|---|
|
md5:bf0d552e10dc1ec421847dcf0bcc5d66
|
225.8 kB | Preview Download |
Additional details
Additional titles
- Subtitle
- A Practical Framework for Sustainable Scientific Software