Every Access project will fail because 80% of what the user wants is easy, the next 10% is possible, and the last 10% is not.—Dietzler's Law
miniblog.
Related Posts
I asked Hermes Agent to change how it set thread titles, and it patched its own source code!
Self modifying code is hard to reason about even in a deterministic environment. I'd already limited Hermes access to the todoist API and web search out of an abundance of caution.
Watching https://youtu.be/KWB-gDVuy_I and I'm struck by how weird constructors are as an API.
* They promote total functions, making it hard to do validation.
* They're hard to split up, because they have special access to unfinished data.
* They're like a framework: you get called.
I'm writing an experimental PL and I want to exercise it on real programs asap. These need to be useful (so I actually try them), but simple (my PL is unfinished).
My current ideas:
* A git fuzzy branch switcher (shell commands)
* dotfiles sync (filesystem access)
Suggestions?