Mentions personal use of NID.

Transcript context

…I think that's one of the things that the learning curve is very steep on right now. So, looking at some of the code that some of these models or agents are writing, they're very hard to follow. It's like, I know I'm getting better performance from this, but I have no idea why. And if this thing breaks, I'm going to have no idea how to fix it. That makes me uncomfortable. Maybe that's because I'm still on that learning curve of, how do we operate in that world? What's the set of tests or rationalization and understanding that we need to have to get comfortable with it? But at first glance, it looks very unfamiliar and very unsettling. So, I think engineering over time will evolve to be comfortable with that, and have fluency in it, and know how to guide new tech, and agents, and new capabilities to make sure that we feel really good about what the output is. I wonder what the metaphor is for this where this... I continue to be astounded by how much engineering has transformed in two years. It's like a completely different dropdown. We used to sit there in NID and write code, and now you're just talking to agents and reviewing code and shipping 100 PRs a day. It feels like it's an acceleration of how much engineering has changed. But if you looked over the last 10 years or 20 years, you would say the same thing. So, there's just something that's moving faster. And it's hard to wrap our heads around how quickly it's moved in the past couple of years. But it's not totally unfamiliar that engineering or data science or product would have these big shifts, just like how filmmaking works. If you look over the last 100 years, it's unbelievably different because of technology and new tools that we've brought to it. Just feels like the cycle is speeding up.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.