The problem is that you never really know whether the chat bot gets it right or terrifically wrong unless you already know how to do the task yourself. And in some cases, paying an analyst $50/hr. for a higher degree of confidence than you can get from a $1 chat bot is still very much worth it. The stakes are higher, too. If the chat bot gets it wrong, what are you going to do, fire it? There goes a small trickle of…
In my experience, in many cases, the so-called "first draft" (of code, content, etc.) is more just helpful for a mental warm-up. It isn't actually suitable. The time it takes to write/code/etc. isnt in the typing, that's trivial. It's in modelling the problem (, audience) and solving it. ChatGPT isnt in the game of modelling problems and solving them, it possesses only superficial semantic characteristics of the ques…
Replacing a SQL analyst with 26 recursive GPT prompts
51–60 of 311 posts
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#52and
> It seems like there’s almost no limit to how good GPT could get at this.
I don't see how that's a valid conclusion given the results. 2 simple things right, moderate to difficult things wrong? Hardly a ringing endorsement.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#53I love those ChatGPT projects! Of course it's silly and nobody is really replacing somebody with a program that confidently get half it's answers wrong. But it's fun to just naively let ChatGPT solve the problem. But I wonder what it's going to look like in a few years. Currently, it's really just a demo that got surprisingly huge traction. I think the most pressing problem is not to get ChatGPT smarter but to get it…
> nobody is really replacing somebody with a program that confidently get half it's answers wrong I gotta tell you, I use copilot to help with my coding, and it still sends a shiver down my spine when it writes the entire database migration based off of the filename, or writes 4 pages of automated tests that work right on the first try.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#54Earlier quoted context omitted.
Yeah, it doesn't. A friend of mine played around with this and on trickier questions you got confidently incorrect answers.
That is almost worse than it completely not working.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#55I love those ChatGPT projects! Of course it's silly and nobody is really replacing somebody with a program that confidently get half it's answers wrong. But it's fun to just naively let ChatGPT solve the problem. But I wonder what it's going to look like in a few years. Currently, it's really just a demo that got surprisingly huge traction. I think the most pressing problem is not to get ChatGPT smarter but to get it…
> nobody is really replacing somebody with a program that confidently get half it's answers wrong I gotta tell you, I use copilot to help with my coding, and it still sends a shiver down my spine when it writes the entire database migration based off of the filename, or writes 4 pages of automated tests that work right on the first try.
Not sure that’s the right criterion to assess the quality and adequacy of tests.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#56"Who were the largest biotech investors in 2022?"
I can think of at least six possible answers based on these questions: 1. Does largest mean dollar amount, or number of investments? 2. Would number of investments count companies invested in or funding rounds invested in? 3. Does largest mean the largest total dollar amount invested in 2022, or does it mean larges dollar amount of new investment in 2022?
It looks like ChatGPT chose the query to mean the investors with the largest dollar amount of new investment in 2022.
When you expand your natural language query to clarify all of these ambiguities, how far away are you from a SQL query? I am not sure, but I think that you are getting pretty close.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#57Re: Replacing a SQL analyst with 26 recursive GPT prompts
#581. Using embeddings to filter context into the prompt
2. Identifying common syntax errors or hallucinations of non-existent columns
3. Flagging queries that write instead of read
Plus lots of prompt finessing to get it to avoid mistakes.
It doesn't execute the queries, yet. For an arbitrary db, it's still helpful to have a human in the loop to sanity check the SQL (for now at least).
Demo at https://www.querymuse.com/query if anyone's interested