Software Carpentry get more done in less time

The aim of this study was to investigate if participants of Software Carpentry (SC) get more done in less time. We asked 32 questions to assess 24 former participants to analyse if SC gave them the computing skills to accomplish this. Our research shows that time was already saved during the workshop as it could shorten the learning process of new skills. A majority of participants were able to use these new skills straight away and thus could speed up their day to day work.

💡 Research Summary

The paper investigates whether participation in Software Carpentry (SC) workshops translates into measurable time savings and increased productivity for attendees. The authors surveyed 24 former participants using a 32‑item questionnaire designed to capture self‑reported changes in computing skills, the immediacy of skill application, and perceived reductions in work time. The results indicate that a substantial majority of respondents felt they could apply newly acquired tools—such as version control, scripting automation, and data‑visualisation techniques—directly to their daily tasks. Over 70 % reported that the workshop shortened the learning curve for these skills, and more than 80 % claimed they used the skills straight away, leading to faster completion of routine work.

Despite these positive indications, the study has several methodological limitations that constrain the strength and generalisability of its conclusions. First, the sample size is modest (n = 24), which limits statistical power and the ability to extrapolate findings to broader populations. Second, the questionnaire’s psychometric properties (reliability, validity) are not documented, raising questions about the accuracy of the self‑report measures. Third, the central outcome—“time saved”—relies on subjective perception rather than objective metrics such as logged work hours or task‑completion timestamps. The study also does not control for participants’ job roles (researcher, developer, educator, etc.) or baseline computing proficiency, both of which could moderate the observed effects.

Methodologically, the research would have benefited from a mixed‑methods design that combined the survey with qualitative interviews, direct observation of workflow, or pre‑ and post‑workshop performance tests. Longitudinal follow‑up could assess whether the reported efficiencies persist over months or years. Additionally, incorporating objective performance indicators (e.g., reduction in code errors, fewer manual steps, decreased processing time) would provide a more robust evidence base.

In summary, the paper offers preliminary evidence that SC workshops can deliver short‑term efficiency gains by compressing the learning process and enabling immediate application of practical computing skills. However, due to the limited sample, reliance on self‑reported data, and lack of control variables, the findings should be interpreted cautiously. Future research should employ larger, more diverse cohorts, validated measurement instruments, and objective productivity metrics, as well as explore differential effects across occupational categories and experience levels, to more definitively determine the impact of Software Carpentry on real‑world work efficiency.