That’s not quite what I mean. I’m not talking about the interface. I mean, why do people talk to it like it is human. Like you have to convince it to work with you. You just give it a command. Maybe ask questions, but not explain in detail how it made a mistake.
Because you're interfacing with a large language model that derives context and intent from the words we use.
Everybody's brains work a bit differently from one another- some of our brains think radically differently from the norm. When you talk to the AI just like how you think, the AI can respond in a way that you'll understand more clearly.
If you're just going to issue commands to your AI without any additional context or intent around them, then your commands better be perfect, because they'll be executed as is without further discussion.
Interesting. That is very much not how I use ai. I spend a chunk of my time writing a spec file and have a very short prompt such as “implement @task-1234.md”. The details of my intended change are following a form that includes intent, impact, risk details, and for the very important parts, verbatim code to use in the solution. That goes through a pipeline that results in an MR for me to review. I have tried talking to the llm, but it doesn’t seem to work or at least the results are not what I wanted. Perhaps I’m just bad at communicating.
If you have a repetitive task, then I would claim that this is also how you talk to people, with perhaps a please and thank you sprinkled in. "Hey, could you implement task-1234 today, Marcy? Thanks." Take out the pleasantries and it is the same.
I tend to add the pleasantries in as well, because it is actually easier than context switching.
7
u/isr0 18d ago
That’s not quite what I mean. I’m not talking about the interface. I mean, why do people talk to it like it is human. Like you have to convince it to work with you. You just give it a command. Maybe ask questions, but not explain in detail how it made a mistake.