sbaltes / pandemic-programming

Scripts used for the Pandemic Programming online survey published in EMSE 2020

Pandemic Programming Survey

We only publish the scripts, questionnaires, recoding instructions, as well the the recoded data in this repository. The raw data is not published, because it contains open-ended responses of our participants, which we promised not to publish. If you reuse parts of this repository, please cite the corresponding research article:

Ralph, P., Baltes, S., Adisaputri, G. et al. Pandemic programming: How COVID-19 affects software developers and how their organizations can help. Empirical Software Engineering 25, 4927–4961 (2020). https://doi.org/10.1007/s10664-020-09875-y

For our analyis script, see this repository.

In the following, we provide the recoding instructions that Sebastian Baltes shared with all co-authors:

1. Download responses as a CSV file:

2. Rename the CSV file to <LANGUAGE>.csv, e.g. English.csv for the English version, and copy it into the data directory. Don't forget to save a backup locally, adding a timestamp as Paul described in his instructions.

3. Update the information in doc/Timestamps.csv. This list should always correspond to the recoded data you put in the data directory.

4. Save a PDF version of your questionnaire using the print function that Google Forms provides. Save that file under doc/<LANGUAGE>.pdf, e.g. doc/English.pdf for the English version.

5. Send the files <LANGUAGE>.csv and <LANGUAGE>.pdf together with the time information to Paul and Sebastian via email.

6. Modify the script preprocessing.R for your language (see comments in the script).

7. Execute the script preprocessing.R, this should generate a file <LANGUAGE>_filtered.csv in the data directory.

8. Modify the script recoding.R for your language (see comments in the script). Please double-check whether the variable mapping is correct, because the question order may be randomized.

9. Execute the script recoding.R , this should generate a file <LANGUAGE>_recoded.csv in the data directory.

10. Create a new local Git branch named <LANGUAGE>, e.g. english for the English version, and push your changes into a new remote branch with the same name.

11. Let Paul and Sebastian know when you have pushed your changes.