F.S. Gürses
Please Note
5 records found
1
Engineering infrastructural power over software production
The case of software-as-a-service
Over the past two decades, vendors have moved the development, operation and maintenance of enterprise software into cloud infrastructures managed by a handful of cloud companies. Critical scholars have recognized this capacity to produce and deliver software at scale–now often referred to as software-as-a-service, or SaaS–as part of cloud companies’ growing infrastructural power. However, while prior scholarship has examined the political economic ramifications of this entanglement, it often treats scalability and infrastructural power as accomplished facts, rather than contested concepts. This article complicates these concepts by examining the emergence of SaaS at a time when neither the scalability nor the infrastructural power of cloud companies was yet stabilized. Drawing on diverse sources, it analyzes Salesforce as a case that provides insight into how incremental discursive and material efforts at consolidating its infrastructural power over software production shaped the conditions under which the deployment of scalable software services to a vast number of client organizations became possible. By foregrounding software production, this article treats scalability as a sociotechnical achievement forged alongside ongoing attempts by cloud companies to establish and defend their infrastructural power, rather than an inherent attribute of contemporary cloud infrastructures. In doing so, it contributes to critical scholarship on cloud computing by underlining the co-constitutive nature of infrastructural power and scalability while situating them as fragile–rather than firmly established and uncontested–outcomes of historical contingencies.
Back-to-the-Future Whois
An IP Address Attribution Service for Working with Historic Datasets
We characterize fairness limitations using concepts from requirements engineering and from social sciences. We show that the focus on algorithms' inputs and outputs misses harms that arise from systems interacting with the world; that the focus on bias and discrimination omits broader harms on populations and their environments; and that relying on service providers excludes scenarios where they are not cooperative or intentionally adversarial.
We propose Protective Optimization Technologies (POTs). POTs, provide means for affected parties to address the negative impacts of systems in the environment, expanding avenues for political contestation. POTs intervene from outside the system, do not require service providers to cooperate, and can serve to correct, shift, or expose harms that systems impose on populations and their environments. We illustrate the potential and limitations of POTs in two case studies: countering road congestion caused by traffic beating applications, and recalibrating credit scoring for loan applicants. ...
We characterize fairness limitations using concepts from requirements engineering and from social sciences. We show that the focus on algorithms' inputs and outputs misses harms that arise from systems interacting with the world; that the focus on bias and discrimination omits broader harms on populations and their environments; and that relying on service providers excludes scenarios where they are not cooperative or intentionally adversarial.
We propose Protective Optimization Technologies (POTs). POTs, provide means for affected parties to address the negative impacts of systems in the environment, expanding avenues for political contestation. POTs intervene from outside the system, do not require service providers to cooperate, and can serve to correct, shift, or expose harms that systems impose on populations and their environments. We illustrate the potential and limitations of POTs in two case studies: countering road congestion caused by traffic beating applications, and recalibrating credit scoring for loan applicants.