Why bother?

Why bother?#

The private payoff#

You are your first replicator…

Efficiency, not just compliance#

Good habits from day 1 pay off long before the journal asks:

  • Fewer, shorter trips to the RDC

  • Re-runs that “just work” instead of yet more debugging

  • Less time lost when an RA leaves

Fewer, shorter RDC trips#

  • Time spent in RDCs is often disruptive

    • Cross-campus, or even cross-country, travel

    • Constraining, unfamiliar environment

  • Students: You will graduate, and work somewhere else!

  • Efficiency in code structure and re-running code is time saved for debugging

Surviving RA turnover#

  • The student who wrote merge_v3_final_FINAL.do quit academia

  • Every student will graduate!

  • Coordination across time and people is aided by good reproducibility

Contents