GitHub affordances as human-agent conveyances

I've been noticing the growing use of GitHub, or rather core GitHub building blocks, as the natural choice for work management between humans and agents. Specifically issues and pull requests. One example close to me and my colleagues is how my friend and boss Tom Jung manages the identification, parcelling and specification of tasks for his agents to work on, as issues in the repo for our tutorial system. Another example is how that work is then managed in the form of pull requests (PRs), which I guess is a natural consequence of the first observation. Incidentally, this makes me think that this also changes the issue mechanism as a conveyance for work items rather than mere problem statements. A net positive, perhaps. Anyway, it's on the topic of PRs that I came across two blog posts from folks I have admired for a long time. In Hide your slop PR descriptions behind <details><summary>, Simon Willison uses HTML's details disclosure element to avoid the TL;DR reaction "I'm not reading…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town