Good LLM devtools are also good human devtools
What does a well designed developer tool (programming language, library, API, CLI utility) look like -- for an LLM? The more we write code with Copilot and Cursor and chat-assistants, the more important this question is.
Off the top of my head, a good tool for LLM programmers:
- Chunks, abstracts and simplifies, so making most usage pretty concise -- to reduce token usage. Then LLM usage is cheaper and faster.
- Makes it straightforward to understand what code is causing a particular behavior, and discourages complex interdependencies across multiple files. Then it is clear what needs to go into the LLM context.
- Is mainstream enough for lots of documentation and bug-related Q&A to be available online. Then it'll be supported by all mainstream LLMs, not just ones specifically fine-tuned for it.
To me, that also seems a good tool for human programmers.
Perhaps there is nuance I am missing, because I haven't built a coding copilot myself. And possibly there is a powerful design space of tools, that LLMs excel at using but humans suck. But my initial recommendation would be to just build good tools; the LLMs will be able to pick it up.