permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

not_doing.mdwn (3392B)


      1 To reduce the resource use and waste generated by technology, embracing 'not
      2 doing' aka 'refusal' is essential for achieving degrowth. Refusal suggests a
      3 starting point of resistance and a deliberate move towards reimagining more
      4 just futures. With computing's potential to be employed in violent and
      5 oppressive ways, refusal and collective resistance and interconnected tools
      6 that need to go beyond simply turning abstract notions of justice and fairness
      7 by creating opportunities to re-evauluate foundational assumptions of technical
      8 projects and thus allowing for active re-imagination of just futures. By
      9 refusing technological inevitablility we enable forms of resistance to emerge
     10 and alternative techno-futures to be considered.
     11 
     12 The history of computing is deeply intertwined with capitalism and militarism.
     13 From playing a role in warfare and geopolitical power struggles to driving the
     14 automation of labor, computing has significantly contributed to the increased
     15 use of resources and fossil energy. The latest example of this trend is the
     16 construction of hyperscale data centers for running generative AI. Despite the
     17 promise of increased efficiency, the [[Jevons Paradox]] applies: higher
     18 efficiency tends to lead to greater resource use. Efficiency is often presented
     19 as a technical solution to a political issue—making decisions about how and why
     20 we use computing on a heating planet—without questioning the extractive
     21 business model.
     22 
     23 Curbing demand through refusal has proven to be one of the most effective ways
     24 to reduce computing’s harm to people and the planet, and that's where the value
     25 of 'not doing' comes in. By observing and questioning what is truly needed, we
     26 bring attention to the broader issues: What is necessary? Who benefits? Who is
     27 harmed? And what are the impacts on the human and more-than-human environment?
     28 
     29 What can YOU do?
     30 ----------------
     31 
     32 **With or without a computer**
     33 
     34 * On a small scale, the act of not doing is itself a powerful contribution to sustainability. Sometimes, the greatest benefit to the planet comes from simply choosing not to act. Enjoy the pause.
     35 * On a larger scale, practice refusal by joining strategic efforts to reject harmful computing applications.
     36 * At a smaller scale, make many small everyday refusals to boycott resource-hungry, harmful (to people and/or planet) technologies or infrastructures, such as Big Tech services, in your workplace or community.
     37 
     38 **When creating and maintaining software, digital tools or infrastructure**
     39 
     40 * Join or organize a tech worker union or strike.
     41 * Collectively refuse to work on harmful technologies.
     42 
     43 
     44 Principle in action & examples
     45 ------------------------------
     46 
     47 Besides the many invisible non-acts of 'not doing', projects of refusal such as
     48 
     49 * The Tech Worker Initiative [no tech for apartheid](https://www.notechforapartheid.com/)
     50 * Activism against the AI powered genocide in Gaza
     51 * Activism against the arrival of data centers in your region such as citizens blocking the build of a Meta datacenter in Zeewolde (NL). 
     52 
     53 But also: 
     54 
     55 * The [SIDN
     56 case](https://www.criticalinfralab.net/wp-content/uploads/2025/04/CIL010.pdf)
     57 illustrates **not doing as a political and infrastructural stance**: refusing to
     58 treat hyperscale cloud migration as inevitable, and instead questioning the
     59 logic of outsourcing critical public internet functions to corporate platforms
     60 like AWS.
     61