Explicit programming strategies
Open accessThe DOI matches its Crossref record; 11 of the 11 references it cites were found in a registry or an index.
Abstract
Software developers solve a diverse and wide range of problems. While software engineering research often focuses on tools to support this problem solving, the strategies that developers use to solve problems are at least as important. In this paper, we offer a novel approach for enabling developers to follow explicit programming strategies that describe how an expert tackles a common programming problem. We define explicit programming strategies, grounding our definition in prior work both within software engineering and in other professions which have adopted more explicit procedures for problem solving. We then present a novel notation called Roboto and a novel strategy tracker tool that explicitly represent programming strategies and frame executing strategies as a collaborative effort between human abilities to make decisions and computer abilities to structure process and persist information. In a formative evaluation, 28 software developers of varying expertise completed a design task and a debugging task. We found that, compared to developers who are free to choose their own strategies, developers given explicit strategies experienced their work as more organized, systematic, and predictable, but also more constrained. Developers using explicit strategies were objectively more successful at the design and debugging tasks. We discuss the implications of Roboto and these findings, envisioning a thriving ecosystem of explicit strategies that accelerate and improve developers’ programming problem solving.
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
Reason, J. (1990) · doi:10.1017/cbo9781139062367 · Cited by 5,108
Learning and Teaching Programming: A Review and Discussion
Robins, A., Rountree, J., & Rountree, N. (2003) · Computer Science Education · doi:10.1076/csed.13.2.137.14200 · Cited by 1,736 · cited 2×
“…novices, finding that while novices have many diverse strategies while programming (McCartney et al. 2007), most of their strategies are either inherently ineffective, executed ineffectively, or interleaved with ineffective strategies (Robins et al. 2003; Murphy et al. 2008; Loksa and Ko 2016a).”
BackgroundPrinciples of mixed-initiative user interfaces
Horvitz, E. (1999) · Proceedings of the SIGCHI conference on Human factors in computing systems the CHI is the limit - CHI '99 · doi:10.1145/302979.303030 · Cited by 1,490 · cited 1×
“We build upon recent work envisioning distributed human computation [53,1], in which humans and computers jointly compute, requiring mixed-initiative interfaces that coordinate human and computer actions [30].”
BackgroundNormal aging and prospective memory.
Einstein, G. O., & McDaniel, M. A. (1990) · Journal of Experimental Psychology: Learning, Memory, and Cognition · doi:10.1037//0278-7393.16.4.717 · Cited by 1,391
Representations in Distributed Cognitive Tasks
Zhang, J., & Norman, D. A. (1994) · Cognitive Science · doi:10.1207/s15516709cog1801_3 · Cited by 1,203 · cited 2×
“Controlled lab studies examining problem solving found that external representations provide memory aids, ease use of information from the environment, structure cognitive behavior, and change the nature of the task (Zhang and Norman 1994).”
BackgroundUsing task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452
Bielaczyc, K., Pirolli, P. L., & Brown, A. L. (1995) · Cognition and Instruction · doi:10.1207/s1532690xci1302_3 · Cited by 422 · cited 1×
“Other studies showed experimentally that explicit training on these general self-regulation strategies (Bielaczyc et al. 1995) or self-regulation strategies specifically related to programming (Loksa et al. 2016b), can cause significant increases in task productivity and programming self-efficacy.”
BackgroundProgramming, Problem Solving, and Self-Awareness: Effects of Explicit Guidance
Loksa, D., Ko, A. J., Jernigan, W., Oleson, A., Mendez, C. J., & Burnett, M. M. (2016) · Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems · doi:10.1145/2858036.2858252 · Cited by 223 · cited 6×
“Other studies showed experimentally that explicit training on these general self-regulation strategies [7] or self-regulation strategies specifically related to programming [46], can cause significant increases in task productivity and programming self-efficacy.”
BackgroundInfluentialSelf-citationThe Role of Self-Regulation in Programming Problem Solving Process and Success
Loksa, D., & Ko, A. J. (2016) · Proceedings of the 2016 ACM Conference on International Computing Education Research · doi:10.1145/2960310.2960334 · Cited by 143
Self-citationIdentifying computer science self-regulated learning strategies
Falkner, K., Vivian, R., & Falkner, N. J. G. (2014) · Proceedings of the 2014 conference on Innovation & technology in computer science education - ITiCSE '14 · doi:10.1145/2591708.2591715 · Cited by 121 · cited 1×
“To explain these effects, some studies demonstrated that self-regulation strategies, such as monitoring one’s work and explicitly evaluating one’s progress and use of time, and self-explanation, were associated with greater problem solving success [57,19].”
Background
Cited by
Razzaq, A., Buckley, J., Lai, Q., Yu, T., & Botterweck, G. (2025) · ACM Computing Surveys · doi:10.1145/3687299 · Cited by 36
How statically-typed functional programmers write code
Lubin, J., & Chasins, S. E. (2021) · Proceedings of the ACM on Programming Languages · doi:10.1145/3485532 · Cited by 18
“Recent work like LaToza et al. (2020)’s demonstrates the power of PoP work for tool design, describing a tool that leverages the PoP strategies theory to make programmers objectively more successful at design and debugging tasks.”
MethodDebugging with stack overflow: web search behavior in novice and expert programmers
Li, A., Endres, M., & Weimer, W. (2022) · Proceedings of the ACM/IEEE 44th International Conference on Software Engineering: Software Engineering Education and Training · doi:10.1145/3510456.3514147 · Cited by 8
Code Review Comprehension: Reviewing Strategies Seen Through Code Comprehension Theories
Gonçalves, P. W., Rani, P., Storey, M.-A., Spinellis, D., & Bacchelli, A. (2025) · 2025 IEEE/ACM 33rd International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc66645.2025.00068 · Cited by 4
“Understanding these aspects of individual code review performance can inform the design of code review tools and practices [51] that support reviewers’ construction of the mental models [47] and in following effective individual reviewing strategies [30].”
Metadata
- Authors
- LaToza, T. D., Arab, M., Loksa, D., & Ko, A. J.
- Venue
- Empirical Software Engineering
- Published
- 2020-03-07
- Volume
- 25
- Issue
- 4
- Pages
- 2416-2449
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W3009126534
- Cited by
- 31
- References
- 11
- FWCI
- 4.18
- Type
- journal article
- Language
- en
- Open access
- green
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: Explicit programming strategies. https://app.cochat.ai/papers/10.1007/s10664-020-09810-1
- The paper
- LaToza, T. D., Arab, M., Loksa, D., & Ko, A. J. (2020). Explicit programming strategies. Empirical Software Engineering. https://doi.org/10.1007/s10664-020-09810-1
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.