I am always surprised when people frame this as an philosophical/ethical debat about using this shiny perfect tool to do our thinking vs doing it ourselves. Maybe that will be a relevant discussion one day, but for now, my daily interactions with LLMs look like a blooper reel.
I am aware that in demo situations, LLMs can do a great job, and the more computational power you allocate, the better the output. But LLMs are cropping up in situations where the objective is to save 5 minutes of work from a human at the smallest cost possible.
A recent example: the other day I was trying to request a gluten-free meal for a flight. The website did not work for some reason (it was greyed out), so I wrote an e-mail to custőmer service. I got back an LLM-generated response (which, to their credit, was fully disclosed in the first sentence) about how I can use the website to request a special meal. If you have questions, call our agents at … . So I spent 35 minutes on hold until I resolved the issue, talking to two agents. The company basically rendered their cheap, async communication channel (e-mail) useless by using LLMs.
I think that, advances in top-of-the-line LLMs notwithstanding, in most situations we will be encountering the budget version. For example, the essay mentions dating apps. I guess that with careful prompt engineering and trying multiple iterations, you could generate convincing romantic responses in such a situation, but most people will go with minimum effort, because that’s the point, it is a labor saving device, why go overboard?
Similarly, I think that an experienced user can use LLMs as a sophisticated search engine to get a quick intro into a topic, which would be useful in an educational setting. But very few students will invest so much effort, when 5% of it gives you mediocre slop that will be better then the median so you pass.
In coding, LLMs can also be a great tool. I have seen people quickly iterate a prototype, understand it, improve on it, and then use it as a basis or write their own version based on what they learned. But again, that requires effort and understanding, and culling inferior output, etc. As opposed to finishing the task in 10% of the time and moving on to the next one, technical debt be damned.