Algorithmic Fairness Perceptions in the Global South: Evidence from Bangladesh on Ride-Sharing, Beauty Filters, and Large Language Models
Ahmed Abdal Shafi RaselAhmed Mustafa AmlanTasmim Shajahan Mim
Aug 2026
Human-computer Interaction
Abstract
Algorithmic fairness research comes almost entirely out of North America and Western Europe, so we know little about how people elsewhere judge the algorithms they already rely on every day. We asked people in Bangladesh directly: a bilingual (Bangla and English) survey of 199 participants rated fairness across three everyday scenarios -- ride-sharing prices that shift with context, AI beauty filters that reshape appearance, and large language models that handle cultural values differently than a human would.
Four patterns stood out. Context changes the verdict even when the outcome doesn't: a 20% price surge during a medical emergency feels less fair than the identical surge on a casual trip (2.00 vs. 2.17 on a 5-point scale, Wilcoxon p = .006), a small effect uneven across income groups (largest among middle-income participants). People already view surge pricing critically in general; context sharpens the judgment rather than creating it. Demand for transparency, consent, and real user control is close to universal: 85.7% to 90.3% of participants want these protections regardless of gender, income, or prior awareness of algorithmic bias. Beauty-filter harm tracks with self-image more than with social pressure people can easily name; feeling personally affected predicts reduced self-confidence tightly (R^2 = .30, p < .001), though the scale's direction is inferred from context rather than guaranteed by labeled anchors. And among participants who noticed specific instances of LLM cultural bias, many could not say why when asked to elaborate -- recognizing bias and being able to articulate it are different skills.
Outcome-only fairness metrics would miss every one of these patterns.
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
Known for his clear and elegant writing style, Bertsekas shaped fields from control and optimization to large-scale computation and artificial intelligence.
