Gabe Pereyra
6 statements across 1 episodes · 3 bullish · 0 bearish · 1 people on the record · first statement Dec 5, 2025 by Gabe Pereyra · said 2 times in 1 episodes since 2025 · across every show →
On the record as a speaker too: Gabe Pereyra's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Sarah Guo (2)
tap a year for its mentions
2025 2 mentions in 1 episode
Everything said about Gabe Pereyra, oldest first
Dec 5, 2025 positive
Pereyra: In Legal AI, the RL Environment Is a Client Matter
“And in legal, that RL environment is a client matter. So you have all of the context of a fund formation, an acquisition, a litigation, and the models are starting to learn. Let me go in the document management system and see if I can find this, go in the data…”
Dec 5, 2025 neutral
Pereyra: Enterprise AI bottlenecks are orchestration and governance, not model intelligence
“When you get to that scale, a lot of the problems we're solving are not just model intelligence problems. They are these orchestration, governance, and kind of all of the enterprise product problems that you run into at scale.”
Dec 5, 2025 neutral
Pereyra: Real software engineering lacks objective unit-test verifiability at scale
“I think you actually have the same problem in programming, where I think in the short term programming is verifiable, where you can look at unit tests, but once you get into real software engineering, like the unit, there is no unit test. It's like I deployed …”
Dec 5, 2025 positive
Dec 5, 2025 neutral
Pereyra: Complex legal drafting lacks binary verifiability for AI reward functions
“For something like generate this merger agreement, it's really hard to just give some binary like this is good or this is bad. And I think this has been like a big research problem, like with all the labs we work with, and also internally, there is just this o…”
Dec 5, 2025 bullish
Pereyra: Narrow AI point solutions fail to leverage generalist model power
“If you had built something where it's like all this does is like check that your Python code doesn't have bugs, which you could have done better with 3.5, like you wouldn't have built something like cursor. And the intuition was just these models can help you …”