Git repository for every live research question
Code that lives in a folder called final_v3_really is code nobody can review, roll back or rerun. Putting every active study under version control, even the scrappy ones, gives each result a commit it came from and ends the week lost to working out which copy produced last month's chart.
First tasks
- List every study you are working on and where its code sits today
- Initialise a repository for each study and commit the code as it stands
- Push each repository to the team git service with restricted access
- Write a three-line readme naming the question, owner and status