Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Twelve irreducible operations (P1-P12) with known physical implementations, and four without, as a basis for deciding which parts of a neural network belong in the analog domain. 114 algorithms are factored into these primes; the paper builds a compiler that decomposes a compute graph, assigns each prime to a domain, fuses multi-computation patterns and minimises domain transitions. Version 3. (i) Feedback as a design principle extends to training: a gradient measured on the mismatched forward path lets the normalization affine absorb per-channel mismatch (0.7-0.95 sigma down to 0.06-0.16 sigma, the analytic least-squares floor); the backward path needs sign concordance with the forward crossbar but not reciprocity, and the tolerable number of wrong-sign channels is zero. (ii) The four 'missing primes' are not operations but the four components a finite circuit lacks relative to a Turing machine, so the line they mark is the circuit/software line rather than the analog/digital line; 0 of 114 algorithms are fundamentally unmappable once a compile-time bound is supplied, and 28 entries change status. (iii) A signal-domain axis and a 21-rule mismatch calculus make the design space tractable: the calculus retrodicts 36 measured numbers with none outside a factor 2 and predicts two unseen composites to 1.00x and 1.05x. (iv) The four open validation gaps of version 2 are closed at circuit level. Corrections to the published record. The headline count of version 2 (107 algorithms, 79 M / 22 G / 6 U) did not agree with the supplementary table it summarised, which has 114 rows and 86 M; the M column and the total were understated by seven. The equilibrium gain error 'below 1e-4' is an ideal-integrator figure and becomes 7.2e-4 at a realistic 60 dB integrator gain. The '0.006 %' common-mode entries were a solver quantisation floor and are 0.0024 % / 0.0007 % with a converged solver. The priority claim that no prior work had implemented normalization fully in analog is withdrawn and the prior work cited. Fourteen references inherited from version 2.1 carried a wrong field and are corrected; each correction and its verification source is listed in docs/errata_v2.1.md inside the code archive. Prior versions. The version 2 / 2.1 preprint is publicly indexed under two version DOIs of this same concept record: 10.5281/zenodo.21138358 and 10.5281/zenodo.21179525. This version supersedes 10.5281/zenodo.21179525. Files. prime_compiler_v3.pdf (paper), supplementary_factorizations_v3.pdf (complete factorization table, 114 entries), prime_compiler_v3_code.zip (compiler source, tests, all circuit testbenches and the experiment records each reported number comes from). Source repository: https://github.com/Biech95/prime-compiler
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.