Mihail Eric discusses AI-native engineering strategies (Part 2)

Helping us debug things and put up PRs when things are broken, but also used by our own salespeople to find out how the product works, find out how to get to the bottom of something. So there's like, interesting questions we've had to answer around the different personalities that HAL has, depending on whether it's talking like a salesperson versus developer. And so systems like this that we built out over time a lot in the last year or so, shout out to Yinja for HAL and John Tracy as well. So you're building a lot in house. Yeah. You also use other tools? We do use other tools. So what is the line? Yeah, builders buy. Was that. Yeah, the builders buy. It's a good question. And we. I think there's this like a thing, a general principle that I generally. Which is like you build to learn and you buy to keep. Or sorry, you buy to learn and you build to keep. Yeah, the other way around. There you go. So you buy to learn and you build to keep. And I think that's generally true here where in the early days when we were still trying to figure out like, you know, get our feet under us a little bit, we were, you know, code reviews. One of them where we spent a lot of time looking at different code review platforms. It turns out today we still use Devin because we've actually still find a lot of value in how the system's been built. So, you know, shout out to the Cognition team. But then along the way we did try out some like SRE tools and you know, we tried some sort of like off the shelf, maybe more like background agent platforms. Decided that it was just given our infrastructure, given how we had set up our own cloud platform, it just made more sense to kind of build this out internally. Of course we're not dogmatic. We are open to revisiting them if something comes out. But here I felt, I think usually we ended up building a house when we felt that there was no mature offering out there. Code review is maybe an interesting example because we did do a whole survey of code review tools maybe over a year ago. And at the time. And I'll show it out. Like Code Rabbit, right? Yeah, Code Rabbit and them. And there's also like Coder. Graphite. Graphite. Graphite. For a while before they got acquired. Like Ellipsis, which. Like YC Company before the fact. But there's a bunch, right? I mean, so there were a lot of folks that we did try and they were okay, but I don't think they had like crossed the threshold of, like, they're immediately useful yet. And so then we kind of, like. We sort of, like, put it aside a little bit. This was, you know, I'm saying, like, well over a year ago. Then we kind of went back to this and sort of organically. I mean, again, shout out to the Devon team and Cognition folks, where we tried it again. I think I had sort of gotten that. Somebody told me, like, hey, you should try this. And, you know, it seems like it's gotten a lot better. And I've been actually during Silas talk during the class last year, and it was just good. And it was picked organically, like. Like, purely vibes, right? Like, this is. There's no way to. There was. Yeah, this. This.