Earlier quoted context omitted.
In your analogy to the Apple II, is there a fundamental problem people claimed for early computers, which didn’t just boil down to “they need to be faster”? There are fundamental limitations to what an LLM can achieve.
You missed the ever-powerful ellipsis in what he said: Today "..." and then it will be solved. It's the most powerful operator in the whole of applied computer science.
Replacing a SQL analyst with 26 recursive GPT prompts
141–150 of 311 posts
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#142Anyone 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…
To me this boils down to Churchhills adage "Don't trust a statistical report unless you fabricated it by yourself". There are so many subtleties when translating business questions into SQL e.g. was the average deal size in the post's "trend" example computed using average/median/geometric mean formula? Should the trend only contain historic or also projected values. No serious report comes without data definitions,…
I think this can also be extended to data tools. I've had so many experiences where a SaaS tool that tries to automate away the manual SQL analysis shows something totally wrong. I tend to "Not trust, verify" anything coming from a SaaS UI when serious business decisions are about to be made based on it.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#143Anyone 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…
I've done too little SQL to be traumatized by it, but I experienced it plenty of times doing more complex data processing on the backend. I would e.g. spend a week on first discussing a solution, then researching both theoretical background and relevant libraries, and finally writing code to do the math and render the answers (probability distributions). I eyeball them, they seem to all match expectations, so I decla…
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#144Anyone 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…
I've done too little SQL to be traumatized by it, but I experienced it plenty of times doing more complex data processing on the backend. I would e.g. spend a week on first discussing a solution, then researching both theoretical background and relevant libraries, and finally writing code to do the math and render the answers (probability distributions). I eyeball them, they seem to all match expectations, so I decla…
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#145Is this a self-hosted GPT model? One of the smaller models? Fine tuned on Crunchbase data? Any insights into how this was put together?
The article describes how the prompt itself is constructed - to include details of the database schema plus some example data rows, followed by the user's question.
The prompt is then sent to the GPT-3 API. The results are then sent through the API a few more times with some extra prompt engineering before deriving the final result by running the SQL against the original database.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#146Earlier 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".
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#147Is this a self-hosted GPT model? One of the smaller models? Fine tuned on Crunchbase data? Any insights into how this was put together?
It's using the GPT-3 API from OpenAI. The article describes how the prompt itself is constructed - to include details of the database schema plus some example data rows, followed by the user's question. The prompt is then sent to the GPT-3 API. The results are then sent through the API a few more times with some extra prompt engineering before deriving the final result by running the SQL against the original database…
Edit: I noticed you edited your comment above with some details. It seems that he used GPT-3 just to create the SQL statement which was then executed locally. So GPT-3 never had the actual data set, just a prompt that included some details of the schema.
As a result I think any sort of "success" here is fairly limited when GPT-3 is blind to the actual data and has limited knowledge of the schema to be able to formulate queries that imply some knowledge of the data.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#148Earlier quoted context omitted.
Maybe 5% of the business/operations people I've worked with would even want to do this. The rest prefer a smart human to walk them through building a report - most of the time this is because they don't actually know what they need, and they actually need an expert to sit down and figure it out with them.
The longer I'm in the business, the more I feel like my value as a software developer is identifying and asking clarifying questions.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#149Earlier quoted context omitted.
Clearly, the correct move here is to replace the entire team with Looker and let every department head create their own dashboards to track arbitrary kpis with no understanding of the product or underlying data model. /s
The correct move seems to be to replace the team with a set of oracle bones. From the very limited information we have it seems to me like the team was used to justify whatever conclusions were already made before consulting them.