11–20 of 104 posts
The protocol for interacting with code is files and text. You need to define an interface for Ai to click buttons? Or to create keyboard macros that simulate clicking buttons? We are all doomed!
This is the equivalent of LSP but for coding agents. So any editor does not have to rebuild an interface to support each and every new one.
I'm fine with treating AI like a human developer: I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again. I call this "prompt coding": https://www.gibney.org/prompt_coding This way, there is no interaction between my coding environment and the AI at all. Just like working…
Very big doubt. AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.
I'm fine with treating AI like a human developer: I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again. I call this "prompt coding": https://www.gibney.org/prompt_coding This way, there is no interaction between my coding environment and the AI at all. Just like working…
> Nowadays, it is better to write prompts Very big doubt . AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.
The new models are much better at reading the codebase first, and sticking to "use the APIs / libraries already included". Also, for new libraries there's context7 that brings in up-to-date docs. Again, newer models know how to use it (even gpt5-mini works fine with it).
I'm fine with treating AI like a human developer: I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again. I call this "prompt coding": https://www.gibney.org/prompt_coding This way, there is no interaction between my coding environment and the AI at all. Just like working…
> Nowadays, it is better to write prompts Very big doubt . AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.
The real issues I'm struggling with are more subtle, like unnecessary code duplication, code that seems useful but is never called, doing the right work but in the wrong place, security issues, performance issues, not implementing the prompt correctly when it's not straight forward, implementing the prompt verbatim when a closer inspection of the libraries and technologies used reveals a much better way, etc. Mostly things you will catch in code review if you really pay attention. But whether that's faster than doing the task yourself greatly depends on the task at hand
Zed should start improving the diff view. It's one of the worst. It does not even have word level diff highlight or split diff view
I'm fine with treating AI like a human developer: I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again. I call this "prompt coding": https://www.gibney.org/prompt_coding This way, there is no interaction between my coding environment and the AI at all. Just like working…
> Nowadays, it is better to write prompts Very big doubt . AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.
I'm fine with treating AI like a human developer: I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again. I call this "prompt coding": https://www.gibney.org/prompt_coding This way, there is no interaction between my coding environment and the AI at all. Just like working…
> Nowadays, it is better to write prompts Very big doubt . AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.
Maybe it's because the libraries I use are made from small files which easily fit into the context window.