Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Why do you think it is anti-curiosity to use LLMs?

"Don't need to study and trial/error to learn about business, I can get business advice in a box".

It's Stack Overflow copy-pasting MkII.



This reads like a comment from a person who has not tried to integrate LLMs into various workflows.

Have you tried making and LLM draft a study plan for you? Kickstarting learning of a new area?

Have you tried making an LLM correct your "homework" for your studies? When you try to learn a new language?

Curiosity is about not being categorical - "It's Stack Overflow copy-pasting MkII." is extremely categorical and thus, anti-curiosity.


>This reads like a comment from a person who has not tried to integrate LLMs into various workflows

This reads like a comment from a person who makes the discussion about the other person.

>Curiosity is about not being categorical - "It's Stack Overflow copy-pasting MkII." is extremely categorical and thus, anti-curiosity.

You could say the exact same thing about someone criticizing regular Stack Overflow copy-pasting as lacking curiocity and hacking spirit. "Oh, that critique is so extremely categorical".

Sorry, "that's categorical" is not the trump card you think it is.


The root for this is a comment that urges to boycott some persons startup because they express that they were thankful for the advice they get from LLMs (a PhD in physics, that is).

Yes, I find that commentary extremely inappropriate. And yes, I am defending my stance in the sub-threads.

But tell me: you say that my critique of a reductionist categorical view on the use of LLMs (it is merely stack overflow...) is catagorical itself? Can you please elaborate on that.


>The root for this is a comment that urges to boycott some persons startup because

I didn't write it so don't care about the "root for this".

I quoted what I was commenting upon: "Why do you think it is anti-curiosity to use LLMs?".

>Yes, I find that commentary extremely inappropriate.

Feel free to do so. Has nothing to do with my comments and it's not a responce to my arguments. It's sidelining them and trying to appeal to outrage and emotion by getting back to what a different person said.


You do enter into a context when you decide responding within a thread - let's see if we can forget this.

Your sentiment is that this is stack overflow c/p style business development. I understand this as: You receive instructions from a third party entity and carry them out verbatim. An because that to use a LLM that is anti-curiosity.

Let's delve into that, shall we?

1. Following instructions verbatim is as old as instructions. You could apply the same sentiment to mentorship, books, and well, Q/A systems. Just to inspire some reflection: Do you think good chefs ever use recipes or is that only bad chefs? It is quite well established that following instructions is key to learning.

2. You say that it is equivalent to follow instructions from an LLM to following instructions from SO - I think this misses a key feature of LLMs: The ability to index them. You can tell them they are care about business development in a narrow sense, to what it is index all future responses. This is realtime interactive and does probe behavior like changing what you index your instructions for, which indeed is the core of curiosity.

Based on this I hold on to my previous statement as a response yo your comment:

> Curiosity is about not being categorical - "It's Stack Overflow copy-pasting MkII." is extremely categorical and thus, anti-curiosity.

I do find that your line of thought is narrow and dismissed the elements to be curious about regarding LLMs.


In my comment I objected to “hacker spirit” and “curiosity” being misappropriated to mean what they don’t (in a way, something opposite); if I wanted to support the call for boycott, I would have written so.

Treating a comment here as endorsing or refuting the entire thread leading up to it is not going to help a nuanced discussion.


>You do enter into a context when you decide responding within a thread - let's see if we can forget this.

Oh, please




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: