Summarize and interpret the results of the survey

[iaindillingham]

In #1, we designed and administered a survey. In this issue, we will summarize and interpret the results of the survey.

The results should help us validate several assumptions. Namely, that most of our existing users:

• typically have a good quality internet connection while working on their code
• struggle with installing all of the dependencies required for OpenSAFELY, especially Python and Docker
• be comfortable using VSCode for writing ehrQL code, and potentially their analysis code
• be using a web browser that will be compatible with Codespaces, with no IT restrictions that would stop them using Codespaces.

Having summarized and interpreted the results of the survey, we should:

• [x] Communicate our findings from the survey

  a. Within the team b. Within the organisation

• [x] Decide within the team that we should continue to focus on Codespaces

[iaindillingham]

Summary of results^1

Summarized on 27th March. 15 responses.

Most people:

• use Chrome (80%) on a work computer (67%)
• always or usually have an Internet connection (100%), which is at home (100%) or work (47%)
• didn't have any problems setting up OpenSAFELY (53%) in a few hours (47%)
• don't have any problems writing/running code (53%)
• write code in Visual Studio Code (73%) or R Studio (40%)
• run opensafely run in Anaconda Prompt, macOS Terminal, or Visual Studio Code (80%)
• haven't used Codespaces (67%)
• but if they have, then they used it for writing/running Python code (100%) for OpenSAFELY (100%)

If people experienced any problems setting up OpenSAFELY, then the problems related to Docker (x3).

If people have problems writing/running code, then the problems relate to Docker (x3), the PATH (x1), and GitHub permissions (x1).

People report that problems writing/running code are time-consuming (x4).

[iaindillingham]

I'm going to close this issue. I presented the results to the team in this morning's Weekly Meeting. We've decided to continue with Codespaces. Whilst I haven't presented the results to the organization, Lucy discussed Codespaces in this week's Team Talks and Weeknotes.