Coding frequency and tools

Coding frequency

We asked our respondents, “In my current role, I write code to complete my work objectives _____”.

Show chart Show table
Coding frequency Count
Never 26
Rarely 28
Sometimes 33
Regularly 71
All the time 55
a Sample size = 213

Access to and knowledge of programming languages

For each of the most popular programming languages from last year’s CARS data, we asked respondents to answer “yes”, “no” or “I don’t know” for the following statements:

  • I know how to program with this tool to a level suitable for my work
  • This tool is available to use for my work

Knowledge of programming tools

Show chart Show table
Programming language Yes Don't know No
C++ / C# 18 16 179
Java / Scala 13 15 185
Javascript / Typescript 19 17 177
Python 123 7 83
R 111 7 95
SAS 91 10 112
SPSS 97 8 108
SQL 91 14 108
Stata 33 11 169
VBA 33 15 165
a Sample size = 213

Access to programming tools

Show chart Show table
Programming language Yes Don't know No
C++ / C# 7 128 78
Java / Scala 31 123 59
Javascript / Typescript 26 123 64
Python 204 4 5
R 196 11 6
SAS 139 38 36
SPSS 113 53 47
SQL 125 66 22
Stata 77 89 47
VBA 65 106 42
a Sample size = 213

Access and knowledge gaps

We used the above data to calculate the number of respondents who have access but no knowledge, access and knowledge, and knowledge but no access for each programming language.

Show chart Show table
Programming language Access only Access and knowledge Knowledge only
C++ / C# 4 3 15
Java / Scala 26 5 8
Javascript / Typescript 14 12 7
Python 81 123 0
R 88 108 3
SAS 65 74 17
SPSS 48 65 32
SQL 49 76 15
Stata 54 23 10
VBA 37 28 5
a Sample size = 213

What are people using code for?

We asked respondents what data operations they do in their work, and whether they use code to do them.

Show chart Show table
Data operation I do this without coding I do some or all of this by coding
Data Analysis 26 163
Data Cleaning 9 132
Data Transfer / Migration 25 57
Data Visualisation 58 103
Quality Assurance 51 134
a Sample size = 213

Coding capability

We asked respondents a series of questions about whether they feel their coding ability is improving in their current role and where they first learned to code.

Change in coding ability during current role

Respondents who had coding experience outside of their current role were asked whether there has been a change in their coding ability during current employment.

Show chart Show table
Coding ability changes Count
Significantly worse 17
Slightly worse 17
No change 25
Slightly better 48
Significantly better 56
a Sample size = 163

Where respondents have learned to code

Respondents were asked whether they had coding experience outside their current role and, if so, where.

Show chart Show table
First coding experience Count
In current role 49
In education 84
In private sector employment 6
In public sector employment 39
Self-taught 22
Other 3
a Sample size = 205

Coding practices

We asked respondents to report how often they make use of each of the coding practices. Please note that while there are many different coding practices listed below, we understand that not all are proportionate for every coding project.

General coding practices

Show chart Show table
Percent
Question I don't understand this question Never Rarely Sometimes Regularly All the time
I use open source software when programming 8.6 12.3 6.4 20.9 20.9 31.0
I follow a standard directory structure when programming 29.4 5.9 5.3 20.9 25.7 12.8
I follow coding guidelines or style guides when programming 2.7 8.0 10.2 30.5 34.8 13.9
I use a source code version control system e.g. Git 8.6 34.8 16.0 11.8 16.0 12.8
Code my team writes is reviewed by a colleague 1.1 5.9 11.2 29.9 28.9 23.0
I write repetitive elements in my code as functions 2.7 9.1 9.6 23.5 33.2 21.9
I collect my code and supporting material into packages 11.2 39.0 13.4 16.0 13.9 6.4
I unit test my code 29.9 21.9 10.7 13.9 15.5 8.0
I write code to automatically quality assure data 3.2 23.5 17.6 29.9 17.1 8.6
My team open sources its code 23.0 41.7 11.8 11.8 9.6 2.1
a Sample size = 187

Documentation

Show chart Show table
Percent
Question I don't understand this question Never Rarely Sometimes Regularly All the time
Analytical Quality Assurance (AQA) logs 22.5 51.3 8.6 8.6 5.9 3.2
Data or assumptions registers 27.8 40.6 12.8 10.2 6.4 2.1
Documentation for each function or class 10.7 23.5 10.2 25.1 20.9 9.6
Code comments 0.5 6.4 2.1 8.0 33.2 49.7
Flow charts 4.3 40.6 21.4 22.5 9.6 1.6
README files 5.9 31.0 12.8 23.0 17.6 9.6
Desk notes 8.0 18.2 12.8 26.2 25.7 9.1
a Sample size = 187

Reproducible workflow packages

We asked respondents “do you use reproducible workflow packages e.g. drake, make or pymake?”.

Show chart Show table
Use reproducible workflow packages Count
Yes 4
No 102
Don't know what they are 81
a Sample size = 187

Source control platform

The number of users of each source control platform.

Show chart Show table
Version control platform Yes
GitHub 58
GitLab 79
BitBucket 2
AWS CodeCommit 0
Cloud Source Repository (Google Cloud) 8
a Sample size = 187

RAP knowledge and opinions

Knowledge of RAP and RAP champions

We asked our respondents whether they had heard of RAP and what their knowledge is of their own department RAP champion.

Show chart Show table
RAP champion knowledge Count
Have not heard of RAP 80
Heard of RAP, have not heard of RAP champions 44
Heard of RAP, does not know department champion 70
Heard of RAP champions, no champion in department 2
Knows department RAP champion 12
a Sample size = 213

Opinions on RAP

We asked our respondents who had heard of RAP the extent to which they agree with the following statements:

  • “I understand what the key components of the RAP methodology are”
  • “I feel confident implementing RAP in my work”
  • “I think it is important to implement RAP in my work”
  • “I feel supported to implement RAP in my work”
  • “I know where to find resources to help me implement RAP”
  • “I and/or my team are currently implementing RAP”

The figure and table show the percentage of respondents who picked each response option. Percentages are out of a sample of respondents who said they had heard of RAP.

Show chart Show table
Percent
Question Strongly disagree Disagree Neutral Agree Strongly agree
I understand what the key components of the RAP methodology are 6.0 24.8 21.8 37.6 9.8
I feel confident implementing RAP in my work 18.0 26.3 24.8 21.1 9.8
I think it is important to implement RAP in my work 3.8 9.0 27.1 36.1 24.1
I feel supported to implement RAP in my work 10.5 22.6 43.6 15.8 7.5
I know where to find resources to help me implement RAP 13.5 36.8 24.8 17.3 7.5
I and/or my team are currently implementing RAP 14.3 27.1 33.8 17.3 7.5
a Sample size = 133

RAP scores

RAP components

The frequencies for each RAP component below are derived from a series of questions on coding practices (see the coding practices page). These were used to calculate scores for each component (0/1) where respondents answered “regularly” or “all the time” to the relevant questions. The list of RAP components used here is based on the RAP minimum viable product guidance agreed by the RAP champions network.

Show chart Show table
Component Type Count
Documentation Basic 44
Peer review Basic 97
Team open source code Basic 22
Use open source software Basic 97
Version control Basic 54
Code packages Advanced 38
Continuous integration Advanced 35
Dependency management Advanced 46
Follow code style guidelines Advanced 91
Function documentation Advanced 57
Functions Advanced 103
Unit testing Advanced 44
a Sample size = 187

Basic RAP scores

Show chart Show table
Basic RAP score Count
0 62
1 62
2 41
3 26
4 18
5 4
a Sample size = 187

Advanced RAP scores

Show chart Show table
Advanced RAP score Count
0 50
1 31
2 29
3 28
4 21
5 16
6 7
7 5
a Sample size = 187