if i had to pick one catchphrase for 2025 it would be “let code die”. i believe pastagang now knows how to let code die.

moving on from the peace that death causes / i think it’s now worth moving onto what comes after that: how to / what it means to “let code grow”


growth is a process. it doesn’t happen in a snap. it happens gradually. it’s continuous change, not discrete snapshots:

letting code grow means writing live running code, one character at a time. it doesn’t mean writing out your code in a separate window and then pasting it in. it doesn’t mean writing it all out ahead of time and then only uncommenting it / running it at the end.

it also doesn’t mean working away at it really quietly and only turning it when you are happy. it also doesn’t mean deciding ahead of time exactly what you’re going to do.

letting code grow does mean playing it out piece by piece as you add each word. it does mean playing the drum even before you’ve picked the bank / playing the non-note even before you’ve picked the scale. it means letting the people around you hear and respond and interleave their sounds around you: rooting in together / double helix / noise.

it’s about control


and what’s more