The DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Improving the CS1 experience with pair programming
Abstract
Pair programming is a practice in which two programmers work collaboratively at one computer, on the same design, algorithm, or code. Prior research indicates that pair programmers produce higher quality code in essentially half the time taken by solo programmers. An experiment was run to assess the efficacy of pair programming in an introductory Computer Science course. Student pair programmers were more self-sufficient, generally perform better on projects and exams, and were more likely to complete the class with a grade of C or better than their solo counterparts. Results indicate that pair programming creates a laboratory environment conducive to more advanced, active learning than traditional labs; students and lab instructors report labs to be more productive and less frustrating.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Cooperative Learning: Theory, Research and Practice
Slavin, R. E. (1983) · Cited by 3,757
Strengthening the case for pair programming
Williams, L., Kessler, R. R., Cunningham, W., & Jeffries, R. (2000) · IEEE Software · doi:10.1109/52.854064 · Cited by 780
Self-citationThe costs and benefits of pair programming
Cockburn, A., & Williams, L. A. (2001) · Cited by 425
Self-citationThe effects of pair-programming on performance in an introductory programming course
McDowell, C., Werner, L., Bullock, H., & Fernald, J. (2002) · Proceedings of the 33rd SIGCSE technical symposium on Computer science education · doi:10.1145/563340.563353 · Cited by 352
In Support of Pair Programming in the Introductory Computer Science Course
Williams, L., Wiebe, E., Yang, K., Ferzli, M., & Miller, C. (2002) · Computer Science Education · doi:10.1076/csed.12.3.197.8618 · Cited by 270
Self-citationGuidelines for the use of pair programming in a freshman programming class
Bevan, J., Werner, L., & McDowell, C. (2003) · IEEE International Conference on Software Engineering Education and Training (CSEE&T) · doi:10.1109/csee.2002.995202 · Cited by 88
Pair Programming in an Introductory Computer Science Course: Initial Results and Recommendations
Williams, L. A., Yang, K., Wiebe, E., Ferzli, M., & Miller, C. (2002) · Cited by 34
Self-citation
Cited by
Salleh, N., Mendes, E., & Grundy, J. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.59 · Cited by 356
Wei, X., Lin, L., Meng, N., Tan, W., Kong, S.-C., & Kinshuk (2021) · Computers & Education · doi:10.1016/j.compedu.2020.104023 · Cited by 241
An Analysis of Using Many Small Programs in CS1
Allen, J. M., Vahid, F., Edgcomb, A., Downey, K., & Miller, K. (2019) · Proceedings of the 50th ACM Technical Symposium on Computer Science Education · doi:10.1145/3287324.3287466 · Cited by 36
Redesigning an Object-Oriented Programming Course
Kaila, E., Kurvinen, E., Lokkila, E., & Laakso, M.-J. (2016) · ACM Transactions on Computing Education · doi:10.1145/2906362 · Cited by 22
Metadata
- Authors
- Nagappan, N., Williams, L., Ferzli, M., Wiebe, E., Yang, K., Miller, C., & Balik, S.
- Venue
- Proceedings of the 34th SIGCSE technical symposium on Computer science education
- Publisher
- ACM
- Published
- 2003-01-11
- Pages
- 359-362
- OpenAlex
- W2074765208
- Cited by
- 303
- References
- 7
- FWCI
- 30.33
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Improving the CS1 experience with pair programming. https://app.cochat.ai/papers/10.1145/611892.612006
- The paper
- Nagappan, N., Williams, L., Ferzli, M., Wiebe, E., Yang, K., Miller, C., & Balik, S. (2003). Improving the CS1 experience with pair programming. Proceedings of the 34th SIGCSE technical symposium on Computer science education. https://doi.org/10.1145/611892.612006
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.