- related to Tools Building Us of course
- a personal anecdote that I like talking about is when I was working on Zamek Interactive Movie, the original conversations with the filmmakers were that there's only going to be a handful of different scenes, and maybe an alternative ending; instead of hard-coding anything I made a simple graph-based tool to let them to describe the interactions without having to change the code, and that ended up exploding into hundreds of scenes, all interconnected; the tool shaped how the movie ended up looking like
- Live-Coding music is very often loop-based, because the tools to create live-coded music favour loops
- generally loops in solo electronic music are what is most often used both to construct more complicated music with just a pair of hands, but also because most live-performance tools are loop-based
- we keep code in separate (usually not too large) files not because that's great, but because of historical limitations - this complicates a lot of things, as you not only have to think about the "business logic" but also how to split it, what to name the files, where to put them in the file system, etc.
- Unison has an interesting approach at solving some of this (the problem of naming files goes away), and I'm curios what else could be done there
- Realtalk (Dynamicland) keeps code on pages, which don't have to be "named" (though collections of the pages often are, for example Geokit ↗)
- 2023-12-05Tools Building Us1