160 points by jonbaer 7 days ago | 78 comments | View on ycombinator
agenticfish 7 days ago |
aleda145 7 days ago |
It's always been possible to massage your data to fit whatwver case you want to make. Previously you had to go through a data analyst and convince them to let go of their principles. Now you can just let an agent figure it out.
So how do you make sure insights are actually shareable (and trustable) with other parts of the company?
I think just exposing the metrics layer is probably the answer here.
It's kind of funny that the industry has tried to democratize data for so long, but now we scramble to restrict access to protect users from making incorrect decisions.
zodwick 7 days ago |
Like for example
>It doesn't know how your company counts revenue, or which of several similar-looking tables is the real one (it is revenue_cpx_new_revised_v2_use_this_one )
This assumption mostly only holds for non-clean data ( which is mostly a result of humans being lazy and backlog being clogged up ). As AI starts building more of the pipelines upstream - this becomes a non-issue.
Even for existing pipelines, I'd expect fixes to move upstream: when an agent encounters ambiguity at query time, the useful output isn't an edit of the context,but a PR that fixes it.
epgui 7 days ago |
moezd 7 days ago |
zkmon 7 days ago |
throwawayblahbl 7 days ago |
lavendermon 7 days ago |
sdevonoes 7 days ago |
Umm, the model knows the same way humans know: either by looking into slack threads/confluence pages/emails… If your model has access to those things, then it can know. And I foresee that in the near future the model can simply have an incarnation as a Slack member, and when context is not enough, they will simply ask people around (and update docs accordingly)
babodabo 6 days ago |
Qiu_Zhanxuan 7 days ago |
photochemsyn 7 days ago |
8by3 7 days ago |
Like a PT for AI's ... Getting them into shape, and fighting strong.
Felger 7 days ago |
phone_book 7 days ago |
This fake job title sounds like what BI analysts or analytics engineers should be doing as part of their job, not a new job. These jobs are the ones that are usually working on the modeling, answering business questions, and making data accessible and would be creating the context, prompts, and evals to make sure it's working as intended. I think really, analytics engineering and BI should be combined.
Michelangelo11 7 days ago |
amelius 7 days ago |
soizi 7 days ago |
nightmoose 7 days ago |
I get that some specialisation is useful, but I would like to see more T-shaped data folks.