Rerunning one of your own past results from scratch
Pick one figure or table you shared at least six months ago and try to regenerate it on your current machine using only what is saved in the project folder. Most people hit a missing file, a changed package or a forgotten manual step within the first hour. That list of failures is the honest starting point for everything else in this area.
First tasks
- Choose one chart or table you shared more than six months ago
- Copy the original output somewhere safe for comparison
- Rerun the analysis on your current machine without asking anyone for help
- Write down every step that failed or needed a guess
- Compare the regenerated output with the original and note any differences
Standard folder layout for analysis projects
When every project puts data, code, notebooks and outputs in different places, nobody, including you in a year, can tell which script made which file. One layout used everywhere, with raw data, processed data, source code, notebooks, outputs and docs in fixed folders, makes any project readable in minutes and lets tools and templates assume where things live.
First tasks
- Sketch the folders your last three projects actually needed
- Write a one-line purpose for each top-level folder
- Turn the layout into a template repository or project generator
- Move your current project onto the layout and fix broken paths
Git repository for every analysis
Analyses kept as folders of files named final, final2 and final_really lose the history of why a number changed. Putting each analysis under git from day one, with an ignore file that keeps out data, outputs and secrets, gives you a timeline you can return to and a single place colleagues can clone.
First tasks
- List every analysis folder on your machine that is not under git
- Create a shared ignore file for data, caches, outputs and credential files
- Initialise a repository for each active analysis and push it to a remote
- Write each new commit message so it states the reason for the change