Cybernetics × Software Culture

Wiener's cybernetics was a theory of steering — you read the compass, correct the error, repeat. Pasquinelli argues this was never really about machines imitating brains but about encoding social cooperation into controllable systems. Then something odd happened: cybernetics as a named field collapsed (Kelly documents three competing autopsies), but its core logic — iteration, feedback, adaptive correction — quietly became the liturgy of software culture. Agile, sprints, continuous integration, A/B testing, DevOps monitoring loops: these are cybernetic practice stripped of cybernetic vocabulary, which means stripped of the political questions Bateson and Wiener were still willing to ask. Software culture inherited the steering mechanism but lost the argument about who holds the tiller — and Tronti's inversion applies here too, because the move from waterfall to agile wasn't a philosophical breakthrough but a response to developers refusing to work like assembly-line operators, the same pattern of autonomy triggering its own capture through new management technique.