diff --git a/chapters/00. Coding Contingencies.md b/chapters/00. Coding Contingencies.md index 083f7f8..2012c0d 100644 --- a/chapters/00. Coding Contingencies.md +++ b/chapters/00. Coding Contingencies.md @@ -108,10 +108,10 @@ These categories are a way to deal both with the software and hardware circumsta -![two wolves template with actor network theory and object oriented onthology](../img/2wolves.jpg) - In a grey zone where Actor Network Theory (Latour) and Object Oriented Onthology (Harman) overlap, we can think to every element in these categories as an actor, or an object. Hence we can afford, on one hand, to delegate the identity of an actor to its relations with others. Here every iteration and every update of the simulation is an event, an exchange between actants. On the other hand, the unknowable nature of the object leaves room for the simulation to dig deeper, to keep renegotiating the object' state exposing different qualities from time to time. +![two wolves template with actor network theory and object oriented onthology](../img/2wolves.jpg) + Programmers are actors that deal with code. They will be grounded into our present and recent history, where people are often defined by what do they do in order to pay the bills. Thank you capitalism™️ for this detrimental reductionism! They are usually human (or groups of), situated within a professional context. Not all of them code for a living, but some live for coding. ```