Jul 2026· International Journal of Computer Science and Artificial Intelligence· Vol 1, pp. 37-43· 0 citations· 11 references
TL;DR
Findings indicate the market has bifurcated by billing model, that capability is increasingly a model-level rather than tool-level property, and that hybrid tool stacks are a rational response to fit-contingency.
Abstract
The market for AI software-development tools has expanded faster than the frameworks used to evaluate it, leaving practitioners to choose among code-completion assistants, AI-native integrated development environments (IDEs), and terminal-native agents on the basis of headline price or benchmark rank — neither of which predicts realised value. This paper makes two contributions. First, it develops the Cost–Methodology–Fit (CMF) framework, an analytical model that treats tool selection as the alignment of a team's dominant workflow with a tool's interaction paradigm and billing structure, grounded in the established SPACE model of developer productivity [1]. Second, drawing on a systematic documentary comparison of leading tools (verified June 2026) and on the conflicting experimental literature — a controlled trial reporting a 55.8% task speed-up [2] against a randomised trial of experienced developers reporting a net slowdown [3] — it derives the central claim that AI-tool value is workflow-contingent, not tool-intrinsic. Because documentary comparison cannot establish causal productivity effects, the paper additionally specifies a reproducible mixed-methods evaluation protocol that adopting organisations can run to measure fit in their own context. We report the framework and protocol, not new empirical outcomes, and state this scope explicitly. Findings indicate the market has bifurcated by billing model, that capability is increasingly a model-level rather than tool-level property, and that hybrid tool stacks are a rational response to fit-contingency.
Keywords: developer productivity; SPACE framework; usage-based pricing; agentic development; evaluation protocol; tool selection
A case study of a coordinated roll-out of AI-devtools at a large Swedish telecommunications company is reported, investigating how developers experience the roll-out and how they anticipate their profession will change.
Andreas Bexell, Rushali Gupta, L. Heander et al.· 0 citations
It is found that AI exhibits significant efficiency issues in programming, and a series of safety and efficiency issues are found in AI programming, such as code redundancy and over-coupling when writing large projects.
An exploratory review of the emerging gray literature, which largely agrees on what a well-engineered loop contains: triggered agent runs bounded by machine-checkable stop conditions, persistent state files, verifier sub-agents, token budgets, and defined points of escalation to humans.
Jai Lal Lulla, Vahram Nersesyan, Seyedmoein Mohsenimofidi et al.· 0 citations
This state-of-the-art review assembles that evidence across a cross-disciplinary corpus spanning software engineering, human-computer interaction, labour economics, security research, governance, and education, finding the early benchmarks saturated but task-level capability uneven.
D. Michels, Mutaz Abu Ghazaleh, F. Lazzari et al.· 0 citations
This paper reviews recent empirical literature to ask what the developer's job is shifting from typing code to directing agents that type code a change often summarized as a move from code generation to code orchestration.
P. N. Nesarajan, P. Thenmozhi, S. A. et al.· International Journal of Inn...· 0 citations
A six-person student team built a full conversational onboarding assistant over one academic term using pervasive AI assistance using pervasive AI assistance, and outlines next steps toward a more robust, replicable costing methodology for AI-intensive development.
Victor Barros de Miranda Neves, K. S. da Gama, Vinicius Cardoso Garcia· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.