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 |
1 |
| Slightly worse |
3 |
| No change |
3 |
| Slightly better |
7 |
| Significantly better |
7 |
| a Sample size = 21 |
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 |
5 |
| In education |
15 |
| In private sector employment |
2 |
| In public sector employment |
1 |
| Self-taught |
3 |
| Other |
0 |
| a Sample size = 26 |
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 |
0 |
12 |
8 |
8 |
48 |
24 |
| I follow a standard directory structure when programming |
8 |
4 |
16 |
8 |
48 |
16 |
| I follow coding guidelines or style guides when programming |
4 |
4 |
12 |
20 |
48 |
12 |
| I use a source code version control system e.g. Git |
4 |
20 |
8 |
8 |
28 |
32 |
| Code my team writes is reviewed by a colleague |
0 |
8 |
24 |
24 |
28 |
16 |
| I write repetitive elements in my code as functions |
0 |
8 |
16 |
0 |
44 |
32 |
| I collect my code and supporting material into packages |
0 |
24 |
16 |
36 |
16 |
8 |
| I unit test my code |
8 |
16 |
36 |
12 |
16 |
12 |
| I write code to automatically quality assure data |
0 |
24 |
32 |
20 |
12 |
12 |
| My team open sources its code |
4 |
52 |
16 |
12 |
12 |
4 |
| a Sample size = 25 |
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 |
20 |
40 |
8 |
28 |
0 |
4 |
| Data or assumptions registers |
16 |
20 |
24 |
20 |
12 |
8 |
| Documentation for each function or class |
4 |
4 |
24 |
20 |
16 |
32 |
| Code comments |
4 |
0 |
8 |
4 |
20 |
64 |
| Flow charts |
4 |
28 |
32 |
28 |
8 |
0 |
| README files |
4 |
8 |
28 |
28 |
20 |
12 |
| Desk notes |
8 |
20 |
16 |
16 |
24 |
16 |
| a Sample size = 25 |
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 |
0 |
| No |
16 |
| Don't know what they are |
9 |
| a Sample size = 25 |
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 |
13 |
| Heard of RAP, have not heard of RAP champions |
4 |
| Heard of RAP, does not know department champion |
3 |
| Heard of RAP champions, no champion in department |
0 |
| Knows department RAP champion |
5 |
| a Sample size = 27 |
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 |
7.1 |
7.1 |
7.1 |
57.1 |
21.4 |
| I feel confident implementing RAP in my work |
7.1 |
21.4 |
14.3 |
28.6 |
28.6 |
| I think it is important to implement RAP in my work |
14.3 |
0.0 |
7.1 |
14.3 |
64.3 |
| I feel supported to implement RAP in my work |
14.3 |
7.1 |
21.4 |
28.6 |
28.6 |
| I know where to find resources to help me implement RAP |
7.1 |
14.3 |
21.4 |
21.4 |
35.7 |
| I and/or my team are currently implementing RAP |
28.6 |
7.1 |
14.3 |
7.1 |
42.9 |
| a Sample size = 14 |
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 |
7 |
| Peer review |
Basic |
11 |
| Team open source code |
Basic |
4 |
| Use open source software |
Basic |
18 |
| Version control |
Basic |
15 |
| Code packages |
Advanced |
6 |
| Continuous integration |
Advanced |
7 |
| Dependency management |
Advanced |
9 |
| Follow code style guidelines |
Advanced |
15 |
| Function documentation |
Advanced |
12 |
| Functions |
Advanced |
19 |
| Unit testing |
Advanced |
7 |
| a Sample size = 25 |
Advanced RAP scores
Show chart
Show table
| Advanced RAP score |
Count |
| 0 |
2 |
| 1 |
2 |
| 2 |
4 |
| 3 |
10 |
| 4 |
4 |
| 6 |
2 |
| 7 |
1 |
| a Sample size = 25 |