Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Research
Abstract
Agent systems rent competence from a model one call at a time. We present Runesmith, an open-source runtime (Apache-2.0) in which models propose, a small deterministic kernel admits, and the runtime changes its own code only on evidence. In one iteration of its Kaizen loop, Runesmith chose a weakness from its own telemetry and a model rewrote its repair organ, the code it repairs software with. With the same cheap repair model and budget, the new organ repaired more than the organ it replaced, 57 against 35 of 162 sessions on 54 fresh tasks, in about half the time per repair (SR7; exact p = 0.000845, below its preregistered Bonferroni bar of 0.0036 and the bar for all 23 sealed comparisons run). In a further sealed test on three large public repositories with one free model (LOC1), the self-improved organ repaired more regressions than the organ Runesmith shipped with (42 against 17 of 168 sessions, p = 0.00278, significant at its Bonferroni level for its three tests); a hand-written trace-aware localization rule repaired more still (65 of 168, mirrored p = 0.00077), so on this family the learned gain is one that a careful designer can also write by hand. In a post-hoc count, 123 of the 124 repairs came with the faulty file in the model's view: what Runesmith kept is a localization policy. LOC1's protocol and result wording were sealed before any outcome existed and publicly timestamped hours before the analysis. Runesmith changed its own problem-solving code and the change helped under seal, while the improvement process itself stayed unchanged; we call this, and only this, a nudge towards recursive self-improvement. With no model available in 104 sealed scenarios, it made no unauthorized change (15 effects lacked their own ledger event, added in 1.0.0). Six of seven earlier sealed tests did not show their effect; all are reported, with code, data and recomputations.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.