Note

This is an “Ephemera” post – a collection of random writing on a topic that I haven’t synthesized into a real post. So basically: it makes no sense. Enjoy.

1: Example, Inc. Reproducibility Policy

At Example, reproducibility is a core responsibility of software engineers. Reproducible code minimizes onboarding requirements and ensures an open, flat software landscape where developers can read and contribute to code across the company. Enforcement of reproducibility metrics like TTR (Time To Reproduce) and the Reproducibility Baseline education ensure that developers can begin contributing to any code in a matter of minutes.

When it comes to reproducibility enforcement, Example has a motto:

If it doesn’t reproduce, it doesn’t exist.

It is your team’s responsibility to ensure RC (Reproducibility Compliance). Failure to meet RC will result in repository deletion by the RC team.

All consequences for RC repository deletion fall on your team. The RC team is protected; they explicitly have zero liability for any outcome after they delete your repository.

2: Some Questions to Ask

• Do you always put your phone, wallet, and keys in the same place when you get home?
• Do other things you own have a designated location?
• If I stole your phone and computer today, could you get your data back ?
• Do you follow recipes?
• Do you use checklists?