Earlier quoted context omitted.
Maybe it's not a position where it is critical that all answers are 100 % accurate. Maybe getting it right every once in a while is enough to pay for the GPT compute time, but not really for analyst time.
Seems like the issue would be you'd generally get results that 'look' right but would never know if they were actually right without going through and... analysing them
Replacing a SQL analyst with 26 recursive GPT prompts
281–290 of 311 posts
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#282Earlier quoted context omitted.
no one wants to automate themselves out of a job, only other people.
We all believe our job is so challenging and has such special requirements that it _can't_ be automated. It requires someone with the kind of experience learned with wisdom over a long time. Blah blah blah.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#283Re: Replacing a SQL analyst with 26 recursive GPT prompts
#284Earlier quoted context omitted.
Maybe it's not a position where it is critical that all answers are 100 % accurate. Maybe getting it right every once in a while is enough to pay for the GPT compute time, but not really for analyst time.
If you're OK with garbage data you don't need ChatGPT - you can probably make up plausible data on your own. Unless you're building some lorem ipsum stuff.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#285There has to be a way to do invariant training for LLMs, they are already mind boggling powerful but if these models could use language grammar files / Table schemas to learn to respond correctly it would be a game changer.
I am curious about the next codex release.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#286Earlier quoted context omitted.
Thats actually my strategy; This makes it so that 1. my quality overall becomes better and my bosses always liked that (doing things per hand are more error prone, not on time etc.) 2. I can go on holiday knowing my company doesn't need me desperate 3. I can spend the free time of actually innovating and bringing more value to the company/product The problem is not automating yourself out of a job but not being able…
Despite productivity generally improving over the last few decades, wage compensation has not. I'm concerned this will continue as a trend with any productivity improvements from these models.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#287Earlier quoted context omitted.
It doesn't seem like you've really replaced anyone with this. You spent 8 hours doing the work that you could have paid an SQL analyst to do in much less. Unless you're saying that your time is worth less than you'd pay the analyst?
I think the idea is that once built it would be a service that could parse a question, then automatically develop and run any query in response. Sounds cool until it produces the wrong results.. then you'll need to hire an analyst to check every query just in case.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#288Earlier quoted context omitted.
Glad i'm not the only one who saw this. Feels extremely overblown. Very impressive, don't get me wrong, and is yet another bridge closer to letting business side do plain text queries. But that said, stuff like this has existed for awhile, and it's certainly not replacing analysts. For a start, this assumes a VERY clean model, which is of course what you strive for, but the moment you step out of FAANG you'll find th…
Still, while it might not be useful yet , can’t it stand its own as an intriguing proof of concept? The first car was hardly ready to replace the horse. But look where we are now.
Modern cars also have a lot of computing power in the form of fairly dumb systems that are good at sensing things and following rules e.g. "based on conditions X, Y, and Z the flow of the fuel injector nozzle should be N". Got a solid track record here too albiet one that's decades long and not millennia.
A tool that replaces a human data analyst needs to do a lot of inference. When I'm translating stakeholder requests into code and reports, it's about 10% coding and 90% human inference. Remains to be seen how good machines can get there.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#289Earlier quoted context omitted.
Seems like the issue would be you'd generally get results that 'look' right but would never know if they were actually right without going through and... analysing them
I'm saying there are applications where you don't have to know! As long as the fraction incorrect is less than 50 % and you have 2:1 odds on the consequences you don't have to know which 50 % are incorrect.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#290Earlier quoted context omitted.
If you're OK with garbage data you don't need ChatGPT - you can probably make up plausible data on your own. Unless you're building some lorem ipsum stuff.
I might not be okay with only garbage data, but data that are correct 60 % of the time may be good enough for some use cases, when it can be had for 1/50 of the price.