Davies writes: "For an accountability sink to function, it has to break a link; it has to prevent the feedback of the person affected by the decision from affecting the operation of the system."
For a good short overview, see this piece by Mandy Brown: https://aworkinglibrary.com/writing/accountability-sinks
[1] https://press.uchicago.edu/ucp/books/book/chicago/U/bo252799...
So... someone could make a Webamp[2] plugin?
And Butterchurn[3] for viz? (Assuming one can plumb in a compatible audio node)
[1] https://docs.iina.io/interfaces/IINA.API.StandaloneWindow
My biggest problem with XSLT is that I've never encountered a problem that I wouldn't rather solve with an XPath library and literally any other general purpose programming language.
When XSLT was the only thing with XPath you could rely on, maybe it had an edge, but once everyone has an XPath library what's left is a very quirky and restrictive language that I really don't like. And I speak Haskell, so the critic reaching for the reply button can take a pass on the "Oh you must not like functional programming" routine... no, Haskell is included in that set of "literally any other general purpose programming language" above.
There's clearly value in XSLT's near-universal support as a web-native system. It provides templating out of the box without invoking JavaScript, and there's demand for that[1]. But it still lacks decent in-browser debugging which JS has in spades.
[1] https://justinfagnani.com/2025/06/26/the-time-is-right-for-a...
I wrote my own open source one here: https://github.com/drivecore/mycoder. Covered on hacker news here: https://news.ycombinator.com/item?id=43177117
I've also studied coding with it and wrote a lot about my findings here:
- https://benhouston3d.com/blog/lean-into-agentic-coding-mista...
- https://benhouston3d.com/blog/building-an-agentic-code-from-...
- https://benhouston3d.com/blog/agentic-coder-automation
- https://news.ycombinator.com/item?id=43177117
- https://benhouston3d.com/blog/the-rise-of-test-theater
My findings are generally that agentic coders are relatively interchangeable and the reason they work is primarily because of the LLM's intelligence and that is a result of the training they are undergoing on agentic coding tasks. I think that both LLMs and agentic coding tools are converging quite quickly in terms of capabilities.
> Have you found a way to share knowledge packs? Any conventions? How do you manage chat histories / old tasks and do you create documentation from it for future work?
I've run into this wall as well. I am working on it right now. :) Here is a hint of the direction I am exploring:
https://benhouston3d.com/blog/ephemeral-software-in-the-era-...
But using Github as external memory is a near term solution:
https://benhouston3d.com/blog/github-mode-for-agentic-coding
I'm particularly fascinated by those last two links, along with your latest post about READMEs. It makes me wonder about a visual specification editor that provides GitHub-like task chronology around the spec, with the code as a secondary artefact (in contrast to GitHub, where code is primary).
(... speaking as another dad just trying to play with my kid.)