News for hackers. Stuff that matters.
Re:ChatGPT Pro by Balgair on Friday December 06, 2024 @01:23AM (#42336950)
One of the main issues that enterprise AI has is the data in large corporations. It's typically a nightmare of fiefdoms and filesystems. I'm sure that a lot of companies would love to use AI more, both internally and commercially. But first they'd have to wrangle their own systems so that OpenAI can ingest the data at all.

Unfortunately, those are 5+ year projects for a lot of F500 companies. And they'll have to burn a lot of political capital to get the internal systems under control. Meaning that the CXO that does get the SQL server up and running and has the clout to do something about non-compliance, that person is going to be hated internally. And then if it's ever finished? That whole team is gonna be let go too. And it'll all just then rot, if not implode.

The AI boom for corporations is really going to let people know who is swimming naked when it comes to internal data orderliness.

Like, you want to be the person that sell shovels in the AI boom here for enterprise? Be the 'Cleaning Lady' for company data and non-compliance. Go in, kick butts, clean it all up, be hated, leave with a fat check.

Re:ChatGPT Pro by CabSauce on Friday December 06, 2024 @01:29AM (#42336986)
You just hit the chatGPT api for every row of data. Obviously. (Only 70% joking.)
Re:ChatGPT Pro by lolive on Friday December 06, 2024 @02:43AM (#42337386)
Guys, ladies, meet Palantir Foundry ! #micDrop
Re:ChatGPT Pro by msy on Friday December 06, 2024 @06:07AM (#42338634)
Glean are already well established in that space.
Re:ChatGPT Pro by lolive on Saturday December 07, 2024 @03:13AM (#42348139)
Did not know that stack, thanks. From my perspective as a data architect, I am really focused on the link between the data sources and the data lake, and the proper integration of heterogenous data into a “single” knowledge graph. For Palantir, it is not very difficult to learn their way of working [their Pipeline Builder feeds a massive spark cluster, and OntologyManager maintains a sync between Spark and a graph database. Their other productivity tools then rely on either one data lake and/or the other]. I wonder how Glean handles the datalake part of their stack. [scalability, refresh rate, etc]