Search arXiv⌕ Search
Home/Archive/arXiv

arXiv · 2610.24935

Theory of Developer Momentum: The Developer's Experience of Progress and the Craft of Maintaining Motion

Arty Starr·Keith Mann·Margaret-Anne Storey
View original source ↗Read source document ↗Export metadata ↓

Abstract

This paper introduces a Theory of Developer Momentum that helps us see the activity of developing software in motion and the skilled craft through which progress unfolds. We define Developer Momentum as the developer's experience of progress and forward motion toward the goal of a task. Our theory disentangles the related constructs of flow state, momentum, and motivation, so we can more clearly see the relationships between them and how they interweave to support progress. In order to make progress, developers build up working context in memory, become immersed in a cognitive puzzle, and gain clarity through motion in uncertain terrain. The theory provides researchers with a rich experiential lens to investigate how developers' cognitive experiences are shifting in emerging AI workflows. Building on prior grounded theory work, we conducted in-depth interviews with a theoretically sampled subset of 12 professional developers, and eight feedback interviews to evaluate resonance and investigate how the theory translates to agentic AI workflows. We followed a Constructivist Grounded Theory approach to construct a theory grounded in empirical data. Our theory contributes a novel paradigm for seeing the motion of developing software at multiple scales and resolutions, seeing the living capacities that support this motion, and expanding what becomes available for improvement, skilled judgment, and craft.

Explore related subjects

cs.SE

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Arty Starr, Keith Mann, Margaret-Anne Storey. 2026-10-18. Theory of Developer Momentum: The Developer's Experience of Progress and the Craft of Maintaining Motion. https://arxiv.org/abs/2610.24935

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Mitigating Risks in Software Development through Effective Requirements Engineering

Problems that originate in requirements are common and expensive in software projects, and they are a recurring cause of late delivery, budget overruns and cancellation. This paper is a narrative overview of requirements engineering (RE) as a means of reducing these risks. It outlines the core RE activities (elicitation, analysis and negotiation, specification, validation and change management) and the kinds of statements a requirements document contains, including the distinction between requirements, domain properties, assumptions and definitions. It reviews the evidence on the cost of requirements defects, together with the main criticisms of that evidence, and compares how the waterfall, spiral, iterative (Rational Unified Process) and agile lifecycles treat requirements. It then discusses stakeholder identification, elicitation techniques and common obstacles to elicitation, and describes practical ways of turning vague or conflicting stakeholder statements, including security and performance expectations, into precise, verifiable and prioritized requirements. The paper is intended as an introduction for practitioners and students who work with requirements but are not RE specialists.

cs.SE↗
arXiv2026

WAFFLE: Finetuning Multi-Modal Models for Automated Front-End Development

Web development involves turning UI designs into functional webpages, which can be difficult for both beginners and experienced developers due to the complexity of HTML's hierarchical structures and styles. While Large Language Models (LLMs) have shown promise in generating source code, two major challenges persist in UI-to-HTML code generation: (1) effectively representing HTML's hierarchical structure for LLMs, and (2) bridging the gap between the visual nature of UI designs and the text-based format of HTML code. To tackle these challenges, we introduce Waffle, a new fine-tuning strategy that uses a structure-aware attention mechanism to improve LLMs' understanding of HTML's structure and a contrastive fine-tuning approach to align LLMs' understanding of UI images and HTML code. Models fine-tuned with Waffle show up to 9.00 pp (percentage point) higher HTML match, 0.0982 higher CW-SSIM, 32.99 higher CLIP, and 27.12 pp higher LLEM on our new benchmark WebSight-Test and an existing benchmark Design2Code, outperforming current fine-tuning methods.

cs.SE↗
arXiv2026

Can Language Models Replace Programmers for Coding? REPOCOD Says 'Not Yet'

Recently, a number of repository-level code generation benchmarks-such as CoderEval, DevEval, RepoEval, RepoBench, and LongCodeArena-have emerged to evaluate the capabilities of large language models (LLMs) beyond standalone benchmarks like HumanEval and MBPP. Thus, a natural question is, would LLMs have similar performance in real world coding tasks as their performance in these benchmarks? Unfortunately, one cannot answer this question, since these benchmarks consist of short completions, synthetic examples, or focus on limited scale repositories, failing to represent real-world coding tasks. To address these challenges, we create REPOCOD, a Python code-generation benchmark containing complex tasks with realistic dependencies in real-world large projects and appropriate metrics for evaluating source code. It includes 980 whole-function generation tasks from 11 popular projects, 50.8% of which require repository-level context. REPOCOD includes 314 developer-written test cases per instance for better evaluation. We evaluate ten LLMs on REPOCOD and find that none achieves more than 30% pass@1 on REPOCOD, indicating the necessity of building stronger LLMs that can help developers in real-world software development. In addition, we found that retrieval-augmented generation achieves better results than using target function dependencies as context.

cs.SE↗