korrents

korrents · piece

Code for Humans and Machines

Adam Tornhill · 2 Jun 2026

Read the piece on adamtornhill.substack.com ↗

3 korrents from this piece ↓

Adam Tornhill did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. Our reading

    The less humans code, the more it is necessary to optimize for design, architecture, and socio-technical fit.

    Their wordsThe less we humans code ourselves, the more we need to optimize for design, architecture, and a socio-technical fit.

  2. Our reading

    Recurring merge conflicts are a sign of socio-technical problems.

    Their wordsSo, let me go out on a limb and claim that recurring merge conflicts are a sign of socio-technical problems.

  3. Our reading

    Recurring merge conflicts indicate a misalignment between the work being done and the architecture supporting it.

    Their wordsRecurring merge conflicts are the canary telling you that there is a misalignment between a) the work you do, and b) the type of work your architecture supports.

Keep reading