Debugging: the good, the bad, and the quirky -- a qualitative analysis of novices' strategies
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
A qualitative analysis of debugging strategies of novice Java programmers is presented. The study involved 21 CS2 students from seven universities in the U.S. and U.K. Subjects "warmed up" by coding a solution to a typical introductory problem. This was followed by an exercise debugging a syntactically correct version with logic errors. Many novices found and fixed bugs using strategies such as tracing, commenting out code, diagnostic print statements and methodical testing. Some competently used online resources and debuggers. Students also used pattern matching to detect errors in code that "just didn't look right". However, some used few strategies, applied them ineffectively, or engaged in other unproductive behaviors. This led to poor performance, frustration for some, and occasionally the introduction of new bugs. Pedagogical implications and suggestions for future research are discussed.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Expertise in debugging computer programs: A process analysis
Vessey, I. (1985) · International Journal of Man-Machine Studies · doi:10.1016/s0020-7373(85)80054-7 · Cited by 359
Successful students' strategies for getting unstuck
McCartney, R., Eckerdal, A., Mostrom, J. E., Sanders, K., & Zander, C. (2007) · Proceedings of the 12th annual SIGCSE conference on Innovation and technology in computer science education · doi:10.1145/1268784.1268831 · Cited by 54
Self-citation
Cited by
Metacognitive Difficulties Faced by Novice Programmers in Automated Assessment Tools
Prather, J., Pettit, R., McMurry, K., Peters, A., Homer, J., & Cohen, M. (2018) · Proceedings of the 2018 ACM Conference on International Computing Education Research · doi:10.1145/3230977.3230981 · Cited by 129
(2019) · doi:10.1145/3287324.3287374 · Cited by 104
Misirli, A., & Komis, V. (2023) · Early Childhood Research Quarterly · doi:10.1016/j.ecresq.2023.05.014 · Cited by 86
Do Enhanced Compiler Error Messages Help Students?: Results Inconclusive.
Pettit, R. S., Homer, J., & Gee, R. (2017) · Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education · doi:10.1145/3017680.3017768 · Cited by 66
Static Analyses in Python Programming Courses
Liu, D., & Petersen, A. (2019) · Proceedings of the 50th ACM Technical Symposium on Computer Science Education · doi:10.1145/3287324.3287503 · Cited by 46
Metadata
- Authors
- Murphy, L., Lewandowski, G., McCauley, R., Simon, B., Thomas, L., & Zander, C.
- Venue
- ACM SIGCSE Bulletin
- Published
- 2008-02-29
- Volume
- 40
- Issue
- 1
- Pages
- 163-167
- ISSN
- 0097-8418 (ISSN-L)
- OpenAlex
- W4240463245
- Cited by
- 118
- References
- 2
- FWCI
- 2.81
- Type
- journal article
- 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: Debugging: the good, the bad, and the quirky -- a qualitative analysis of novices' strategies. https://app.cochat.ai/papers/10.1145/1352322.1352191
- The paper
- Murphy, L., Lewandowski, G., McCauley, R., Simon, B., Thomas, L., & Zander, C. (2008). Debugging: the good, the bad, and the quirky -- a qualitative analysis of novices' strategies. ACM SIGCSE Bulletin. https://doi.org/10.1145/1352322.1352191
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.