Sep 2026· Zenodo (CERN European Organization for Nuclear Research)· 64 citations· 42 references
Abstract
Version 2 (2026-08-04). Revised to the NLL Universal Paper Format v6. The original text is retained in full; nothing has been deleted. Corrections appear as marked blocks placed at the section that carries the claim, and each one states what the paper said, what the data show, the corrected claim, why it happened, and what still stands. This version adds apparatus and two scoping lines; no claim is retracted.The paper claims only what it measured, discloses that the decay is applied in software rather than on-chip, and correctly disclaims mechanism novelty against Pehle et al. (2022) and Cramer et al. (2022).Two notes: five consecutive days cannot bound drift, as the paper states; and the Vairāgya framing is a label rather than a mechanism, which the paper's own scope note concedes. Chip access route added to Data availability. Everything below this line is the original description from version 1. It is retained unchanged for the record. Where it conflicts with the corrections above, the corrections stand. Two framings it repeats have since been withdrawn in full — the Bhaya Quiescence Law and the Buddhi S-Curve. Both are addressed in Maya-Meta P1, now superseded, and in the self-audit of Maya-Meta P2. Maya-Sutra P1: Letting Go on Silicon characterizes, on real analog silicon (BrainScaleS-2), how a single neuron stops firing ("lets go") as its input synaptic weight is reduced. Using a minimal in-the-loop protocol — set a weight, deliver a fixed five-spike burst, count the resulting spikes — we report five properties of this Vairāgya (non-attachment; the forgetting mechanism) signature. (1) The decay curve is reproducible within a session (maximum spread 0.47 spikes across three identical runs). (2) The shape is rate-invariant in weight-space; an apparent rate-dependence in round-space is a sampling artifact. (3) The weight-to-firing response is a soft staircase whose analog noise is localized at a let-go edge, with near-noiseless plateaus. (4) Across five consecutive days on independent nightly calibrations the shape reproduces while the absolute edge drifts within a bounded band (weights 37–39, mean 38.2). (5) Across a 32-neuron sample the staircase is the majority behaviour (~78% once the measurement window is widened), with neuron-to-neuron fixed-pattern variation dominating day-to-day calibration drift. The underlying analog mechanisms — soft firing thresholds, fixed-pattern heterogeneity, calibration drift — are known BrainScaleS-2 physics; no mechanism-level novelty is claimed. The contribution is a clean, honest characterization, the Vairāgya lens with predictions the hardware can falsify, and the neuron-reliability groundwork required before a property confirmed on digital substrates can be credibly tested on analog silicon. Two artifacts were caught and rejected, not published: a rate-space "linger" that proved to be a sampling artifact, and two stale-file uploads detected by a timestamp-and-noise check. Scope-lock per Maya-Meta P2: all findings are reproducible signatures within THIS architecture under THIS protocol — Property, not Law; a characterization and reliability baseline, not new physics and not a claim about biological brains or all chips. Series: Part of the Maya-Sutra Series — Nexus Learning Labs' hardware-native track, characterizing neuromorphic substrates directly (one substrate, one honest characterization at a time) as the foundation for cross-substrate confirmation of the Maya program's properties. Research characterization only. Links: GitHub Repository (private — to request access: email research@nexuslearninglabs.in with subject "Code Access Request — Maya-Sutra-P1" and your research context) | Interactive Dashboard | FAQ | Full Series Index — nexuslearninglabs.in Nexus Learning Labs, Bengaluru · UDYAM-KR-02-0122422 · BHASKAR IN-0526-9452JS · ORCID: 0000-0002-3315-7907 · VAIRAGYA_DECAY_RATE = 0.002315 — an ORCID-derived provenance mark, not an experimental parameter. Each paper's disclosure block states whether it reached a result in that paper. · Canary: MayaNexusVS2026NLL_Bengaluru
Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 728 citations· ⚡54
Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduAug 17, 2026
A USAF cadet and a Lincoln Laboratory researcher found AI chatbots can help nontechnical service members produce viable software applications for their unique problems.