Earlier 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…
>the moment you step out of FAANG Even in FAANG, most data is going to be extremely messy. * There's usually very little incentive for good documentation, so you have to guess what the table contains based on column names and exploring patterns in the data. * Enforcing a single pattern/process for data across the entire org is a pipe dream. * Logging tables are written to by hundreds of engineers across dozens of tea…
Replacing a SQL analyst with 26 recursive GPT prompts
181–190 of 311 posts
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#182How exactly does one incorporate data that the GPT was not trained on into ChatGPT?
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#183Re: Replacing a SQL analyst with 26 recursive GPT prompts
#184Hmmm... I'm surprised I'm not seeing anyone else question the validity of this taking "2 hours" Given that it's written on the blog for the product it's using, this reads to me a lot like a pure sales pitch. They want us to believe if you use Patterns (which is neat), your company will be much more cost-effective. I'm not saying that's bad - that's probably the right thing to do with their company blog, and it's cool…
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#185You didn't replace a SQL Analyst, you just gave them a query generator. End data consumers don't understand the data model, assumptions, quirks, etc. If they fire the analyst, they are going to wind up drawing a lot of bad conclusions on anything more complicated than simple aggregations.
You can easily add more components to start thinking about models/assumptions/etc, like adding interfaces to Data Catalogs (i.e. Glue Data Catalog). As part of a POC I made, I built a similar bot without recursion for debugging and iterative query building though. It does the following: - It predicts most probable entities from the question. - Searches AWS Glue Data Catalog for the most probable/useful tables. - It b…
It’s a neat tool for analysts as a query generator - I would use it in situations where I’m not familiar with the schema, but it would become less useful as I learn.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#186You didn't replace a SQL Analyst, you just gave them a query generator. End data consumers don't understand the data model, assumptions, quirks, etc. If they fire the analyst, they are going to wind up drawing a lot of bad conclusions on anything more complicated than simple aggregations.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#187Earlier quoted context omitted.
You can easily add more components to start thinking about models/assumptions/etc, like adding interfaces to Data Catalogs (i.e. Glue Data Catalog). As part of a POC I made, I built a similar bot without recursion for debugging and iterative query building though. It does the following: - It predicts most probable entities from the question. - Searches AWS Glue Data Catalog for the most probable/useful tables. - It b…
Thats not really fair to the human. The time to learn basic SQL may be longer, but the algorithm will never develop intuition or independence, while many junior analysts will eventually operate effectively on their own. It’s a neat tool for analysts as a query generator - I would use it in situations where I’m not familiar with the schema, but it would become less useful as I learn.
But hell, as an analyst I would've paid a lot for a tool that searched intelligently through giant datawarehouses (or whatever consultants call them now) and at least gave you probable matches.
Now that same thing exists and you can even finetune its "DSL" towards your own organization.
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#188> this is shockingly close to replacing an entire role at companies with only a couple hours of effort. and > 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
#189Side/meta-question: Do you all think that GPT and such will see a pattern of usefulness starting with: 1) blatantly wrong but helping to train/give examples to the most rudimentary and beginning stages of people learning a task? (since that's what it's doing at the same time?) I.e. replacing low-skilled intro training, or more charitably, helping to make it possible for far more people to learn something with assista…
Meta-Meta question: Why is "actually worrisome" part of "more capable"? If worrisome is because of job prospects for an existing career, my advice is to embrace new tech, not fear it. Just keeping up with things even if you don't use it right away is usually enough to stay relevant. Things don't really evolve that quickly, and so as long as you don't resist change completely things usually work out. Heck even if you…
Re: Replacing a SQL analyst with 26 recursive GPT prompts
#190Hmmm... I'm surprised I'm not seeing anyone else question the validity of this taking "2 hours" Given that it's written on the blog for the product it's using, this reads to me a lot like a pure sales pitch. They want us to believe if you use Patterns (which is neat), your company will be much more cost-effective. I'm not saying that's bad - that's probably the right thing to do with their company blog, and it's cool…
Wasn't sure of their proposition/hadn't heard of them.
> Run and deploy web apps, task queues, massively parallel compute jobs, machine learning models, GPUs, and much more with a single unified framework for code and infrastructure.