Eventually can he store good queries? Or does he have to do the loops each time?
Replacing a SQL analyst with 26 recursive GPT prompts
61–70 of 311 posts
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#62Is this a self-hosted GPT model? One of the smaller models? Fine tuned on Crunchbase data? Any insights into how this was put together?
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#63Earlier quoted context omitted.
> He randomly ended up as the manger of the data analytics team despite no analytics background I assure you, it wasn't random. It was punitive. ;)
Honest question: how rampant is this kind of bullshit politicking in tech companies, and how does this differ with industry, size, company age, etc.? My friends who have worked at big names like F and T have described the cultures there as following: "it's as if everyone who studied too much in high school and college missed all the parties and bullshit, so they're making up for it 'on campus' here". And the stories…
I'm pretty sure the GP was a joke.
Whoever made the decision very likely wasn't intending to punish the person. It was only the consequence.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#64> needs an ilike instead of like
The following query appears to have ILIKE and not LIKE. Am I missing something?
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#65While this is very cool, SQL was designed to be used by business people. We need to go back to that model, where we train the business people who need these analytics how to use SQL to uncover the result. That along with a rigorous policy for including the queries that produced the result so the query logic can be checked would go a long way to actually taking advantage of the data we're collecting as businesses.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#66I think the first piece of feedback you would get would be that the numbers weren't formatted as currency.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#67Anyone who's been asked more than a couple of times for data that requires a non-trivial bit of ad-hoc SQL will know the sinking "oh shit" feeling that comes when you subsequently realise you borked the query logic in some subtle way and have accordingly emailed out a completely bogus answer/report. From the article it doesn't seem that GPT is significantly better or worse than a human in this regard, although an exp…
20 years ago I Knew a sql analyst that would write his tests ahead of time.
Give X data, report should be Y. He would then figure out the SQL. He Didn’t know any other programming. This was before TDD took off. Blew my mind.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#68Based on the natural language query provided, "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…
Fully agree, the next iteration of this should get the model to prompt you when it discovers ambiguity in your request.
User: "Who were the largest biotech investors in 2022?"
Result: For clarification, do you mean:
1. Largest number of investments?
2. Largest total dollar amount invested in 2022
3. Largest dollar amount of new investment in 2022?
4. Something else
User: option 3
Result: Okay, here are the results and query I used.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#69Earlier quoted context omitted.
> GPT is a form of general intelligence. Is it really? I hadn't heard that
no it's not. It's just a neural network. Although it's impressive nobody is seriously calling it "general intelligence".
> nobody is seriously calling it "general intelligence"
Well, I can spot somebody just two messages above you on the thread.
I imagine we will see a lot of people seriously pushing for chatGPT and friends to solve formal problems, take some money, and move away just before some spectacular failure happens.
That will probably also make people very suspicious of AI. (Not that I see any problem with the PR issue.)
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#70SQL is a very high-level language, doing a lot of stuff in very few lines. When I write a web backend, most of the real logic ends up being in SQL. If AI is going to write code that I can trust, it'd probably be SQL first, but not yet.