Posted by gdudeman 20 hours ago
I have a collection of tools I've built in this way here: https://tools.simonwillison.net/python/
#!/usr/bin/env -S uv run --script
https://treyhunner.com/2024/12/lazy-self-installing-python-s...I don't think requiring all CLI tools to be "native binaries" makes sense. Plenty of popular CLI tools are not compiled binaries. The Python and Node.js ecosystems run on those.
For instance, I am adding bluetooth capabilities to my app, and the bluetooth manager can be quite large, to the point where the LLM context window starts to become an issue.
When it gets to that point, the LLM can start making suggestions that don't make sense; it's starts forgetting what you had already done, it can start making architectural suggestions that contradict what you had been doing before. So if you follow them, you end up in this weird state mired in conflicting decisions. Almost like design by committee without the committee.
It's important to recognize this when it's happening rather than just blindly following what it suggests, so some expertise at engineering is still necessary even though the LLM can write okay Swift code.