"It's opt-out, but it's easy to change." We really need objective usability measures to be applied to ensure it really is easy.
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.
Should code completion offer private methods/fields?
If the user chooses a private method, you can offer a quickfix to change its visibility. It's clutter though.
I frequently find myself wanting fields that I haven't exposed yet, and frustrated that the IDE hides them.
Is there a good canonical name for autofixes, where a static analysis tool can apply a change to resolve an issue?
Clang calls them fix-its, LSP calls them quickfixes.