Urgent.News

What's breaking now, across thousands of outlets.

Tech

Overcoding is a second articulation — Deleuze and Guattari on folding sediment into structure, and a plant whose rows never settle

Before the book talks about faces, it talks about rock. In "10,000 B.C.: The Geology of Morals", Gilles Deleuze and Félix Guattari describe how a stratum forms, and they use the geologist's word for the first step: sedimentation. Layers are laid down one after another, each deposit following a statistical order. Sedimentation alone does not make a rock. A second process has to fold the layers…

Before the book discusses faces, it focuses on rock. In their 10,000 B.C.: The Geology of Morals, Gilles Deleuze and Félix Guattari explain how a stratum forms through sedimentation, a process in which layers are deposited one after another in a statistical order. However, sedimentation alone does not create a rock. A second process, known as the second articulation, folds these layers into a stable, functional structure. This folding is what they later refer to as overcoding.

The second articulation can be seen as a fold, similar to how a protein fiber folds back on itself to form a compact structure. This fold is a second kind of segmentarity, working at a different scale than the lower order of molecules. The authors emphasize that overcoding only occurs at the level of integrations, implying a difference in magnitude between the summarized elements and the summarizing entity.

For instance, a headline on a dashboard, which is a short, green or red word, represents a summary of multiple observations that may not agree with each other. This fold separates the headline from the individual sensor rows beneath it, centering, unifying, and finalizing the information presented.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at dev.to →

More in Tech

When a Chargebee Retry Meets a Card That Was Already Replaced

Every billing team has lived some version of this scene. A subscription payment fails on a Tuesday. The retry schedule does its quiet work, the customer gets an email, clicks through, and updates…

  • Retry schedule sends email to customer for card update
  • Conflicting invoice records cause sequencing problem
  • State machine treats paid invoice as terminal signal

Account Updater Is Not a Dunning Strategy: A Braintree Checklist

Braintree's Account Updater is genuinely useful, and that is exactly why it causes a particular kind of trouble: teams enable it, watch a share of failing cards quietly heal themselves, and conclude…

  • Categorize failed transactions by decline type, not date
  • Evaluate updater's effectiveness by tracking resolved card-related failures
  • Examine retry logic and its impact on payment attempts

How does a network know it's wrong?

Loss functions turn every mistake into one number. Here's how squared and absolute loss score the same misses very differently. A neural network can't feel embarrassed when it's wrong.

  • Network learns by minimizing a single number from loss function
  • Squared loss highly sensitive to large errors
  • Absolute loss less sensitive to outliers

More from Saturday 31 October →