Feb 11, 2026 · 48 min · 14 segments
In this episode, Tara Hernandez shares what 18 months of rigorous AI experimentation taught her at MongoDB — including why the initial results showed negative ROI, and where her team eventually found…
that's a very clear remit um to start with of like take these two things and make them one thing where it makes sense to make them one thing right yeah and outcome is also like pretty clear there's not a lot of this is what i what i well i don't know you can tell me i'm wrong but this is the kind of thing that sounds like what i would call just work
It's, How do you take a group of people and get them moving in the same direction procedurally, culturally, in the most efficient way possible for the ultimate end goal, which is the, you know, ideally the relative rapidity of quality software releasing, right? And what does it take to do that? When I went to Pixar, you know, Pixar was a movie studio, still is a movie studio.
And back in the late 80s and early 90s, and then into the, let's see, when did I start there? 2002, the early aughts, right? That was, they were just starting to realize, okay, we had a more academic approach to The managers in what was called the Studio Tools organization were all PhDs with many patents.
These people have written books, right? And the hierarchy felt more like sort of academia.
And then they realized, well, okay, we want to make movies faster than every four to five years.
But using branching, using version control, that was not 100%, right? How to do version libraries, having a proper build system, having a CI system, having a bug tracking system that didn't require you to write SQL statements.
it was reasonably normal then for companies to have not figured this out, especially like Pixar is in the vicinity of movies.
that's a very clear remit um to start with of like take these two things and make them one thing where it makes sense to make them one thing right yeah and outcome is also like pretty clear there's not a lot of this is what i what i well i don't know you can tell me i'm wrong but this is the kind of thing that sounds like what i would call just work
It's, How do you take a group of people and get them moving in the same direction procedurally, culturally, in the most efficient way possible for the ultimate end goal, which is the, you know, ideally the relative rapidity of quality software releasing, right? And what does it take to do that? When I went to Pixar, you know, Pixar was a movie studio, still is a movie studio.
And back in the late 80s and early 90s, and then into the, let's see, when did I start there? 2002, the early aughts, right? That was, they were just starting to realize, okay, we had a more academic approach to The managers in what was called the Studio Tools organization were all PhDs with many patents.
These people have written books, right? And the hierarchy felt more like sort of academia.
And then they realized, well, okay, we want to make movies faster than every four to five years.
But using branching, using version control, that was not 100%, right? How to do version libraries, having a proper build system, having a CI system, having a bug tracking system that didn't require you to write SQL statements.
it was reasonably normal then for companies to have not figured this out, especially like Pixar is in the vicinity of movies.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.