English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Predictive policing is built on a simple assumption: crime exhibits predictable patterns, which means future crime risk can be forecast using historic crime data. While critics have raised concerns over the use of biased data in these systems, less is known about how software is actually used within infrastructures of governance. Drawing on interviews with software developers and an analysis of technical, promotional, and academic materials, I show how internal and external pressures separate predictive policing from the concrete practices it attempts to transform. I argue that predictive policing is a modular technology, plugged into the black box of policing. This modularity separates software developers from the practices they attempt to transform, while enabling them to deflect criticism away from the programs they build. Modularity also means that software can be reconfigured and connected to other systems, which threatens to undermine the set of best practices that guide its development.

“It makes almost no difference which algorithm you use”: on the modularity of predictive policing