Explicit programming strategies

• DOI: 10.1007/s10664-020-09810-1
• Publication Date: 2020-03-07T13:02:27Z
• Authors: Thomas D. LaToza; Maryam Arab; Dastyni Loksa; Amy J. Ko
• Keywords: FOS: Computer and information sciences; test-driven development; 000; 05 social sciences; Computer Science - Human-Computer Interaction; Software development; 02 engineering and technology; Computer programming; Software debugging; Human-Computer Interaction (cs.HC); Software Engineering (cs.SE); computer programming; software debugging; Computer Science - Software Engineering; Test-driven development; software development; 0202 electrical engineering, electronic engineering, information engineering; 0503 education

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.