As computational systems that process multimodal behavioral streams (e.g., speech, gaze, facial expressions, gestures, and bodily movements) become increasingly capable, the field faces a critical question: does more embodied data necessarily yield deeper human understanding? This question is most visible in the gesture recognition community, where machine learning pipelines classify individual gestures against fixed taxonomies: such systems may recognize bodily signals while missing the situated actions those signals help accomplish. This is the recognition-consequence gap, the ontological divide between classifying bodily movements moment-to-moment and understanding what embodied action accomplishes in interaction. Drawing on social science perspectives that treat gesture as a cognitive, communicative, and interactional resource, gesture consequence is proposed as a theoretical reorientation for machine interpretation of gestures. Gesture consequence shifts attention from the classification of individual movements to the unfolding effects of embodied action across interaction, asking from a broader lens how gestures are taken up, ignored, repaired, mirrored, or transformed over time in social interaction. When multimodal systems classify gestures without account for how they are taken up in human interaction, these systems risk producing narrow accounts of human activity that leave out the meanings and forms of participation that unfold through the body.
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
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.