Mixed-methods study shows process management tools enhance learning outcomes in programming.
Background and Context: Today’s software industry increasingly values intricate conceptual knowledge (e.g., sufficient expertise to fix AI-generated code). Though program comprehension and scaffolding have mature literature, the intermediate-to-expert transition for programmers is underresearched relative to its socioeconomic impact. Learner-focused inspection tools exist (e.g., Ply, Isopleth, Python Tutor), but these often address specific problems (e.g., implicit CSS dependencies, async JS, call stacks), without systematic guidance for developing deep conceptual models of architectures and techniques across large real-world codebases or interactions. Objectives: We aim to support non-experts in learning holistically from professional code and to understand how they explore and learn in this context. Given that learners outnumber expert instructors who can teach these concepts, we propose Process Management (PM), a framework for designing tools that scaffold sensemaking on underused yet plentiful real-world code. PM addresses core obstacles learners face (code complexity, surface-level focus, and transfer challenges) through core design principles (intuitive sensemaking processes, comparison, reflection). After prototyping and piloting over five years, we developed three PM tools that surface JavaScript, CSS, and Python techniques. In this work, we seek to understand the effectiveness of PM tools, and the processes learners follow with and without PM support. Study Methods: We report on think-aloud studies conducted over 1.5 years to evaluate our three PM tools. Data include \(~\) 300 hours of remote observation of intermediate-level developers using these tools or controls (Chrome DevTools, VS Code). There were 5 participants in each condition for each tool. Studies consisted of tool training and pre-test, tool-use, and post-test phases, followed by a post-study interview. We qualitatively coded pre/post and tool use data, and present learning gains and in-task behavioral metrics. Findings: Our mixed-methods evaluations show PM tool users explored effectively (e.g., comparing, mapping) and achieved \(~\) 3X more learning outcomes (e.g., conceptual clarity, transferable patterns). Such outcomes were observed consistently across the three programming domains under study. Our qualitative data shows how PM tools can shape learners’ exploration order and process, enhance their understanding of nuanced techniques through interactive comparison, and help them uncover the domain-specific rationales behind design pattern usage through analogical mapping and reflection activities. Implications: Finally, we discuss PM's potential impact on cognitive load, the role of experts today, and a sketch for how LLMs may scale process management. In particular, we envision a world in which educators and builders can develop PM systems that provide intermediate-level engineers a process for learning holistically from open-source professional code to gain conceptual expertise, which they can then use to refine AI-generated code. We also provide examples of LLM prompts that can be used to potentially automate aspects of our PM tool-use sessions, laying some groundwork for AI-driven professional development. In summary, our work contributes to computing education by introducing a scalable and forward-looking tool-building framework and design paradigm for helping intermediate-level learners extract expert-level concepts from complex, real-world code.
No takes yet. Share an insight, caveat, or question.
Dasu et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: