Mihail Eric discusses Git alternatives in software development (Part 3)

That's where we've invested quite a bit. So I push back on that because to me, of course, it's, you know, bare minimum. It should be internally consistent with the PR space. Sure. No, what I meant is the spec for the feature, the code base, because that is the summation of all PRs. That is like if your PR spec got it wrong or missed something, it's going to be the delta between what the whole code base or the whole history of the code base is supposed to do versus what your PR is trying to do. I don't expect you to have an answer because I really stress about this. My try to instruct models to do it. They're bad at it. That's it. So the humans are the spec gods of like, well, five weeks ago I did this other thing and now you're reversing it. Have you, have you seen the post from Basis? Like, they have a. They had a tweet, tweet, little thing, tweet article. I thought they did a great job talking about like different sort of file artifacts they track via git. And some of them are like the specs, the intent of what is to be. And the other is like what they call like the canonical state of the code, which is like a little bit more. Maybe what you're describing is implicit knowledge, implicit intent. That also has to be codified somewhere. Right. So that part that's all version controlled. And I think they found that to work for them. So that might be another thing to share as well. Trying to pull it up. This is Basis, the accounting company. Exactly. Right. Yeah, yeah, we're. We're having Mitchell at my New York conference soon. Yeah, talk to him about that. I like that they are coming up with this. My solution for this is. I don't know if like how ready I am to talk about it because I may never ship. It is something that is replacing git in order to capture all of this. So I call it a program database where it captures all, traces and all and reifies specs to something that we can ignore and keep. And it also controls the skills that are attached to it as well. That's cool because I think basically git is only focused on code and then you just need a source of truth that is not only everything else outside the code, including the implicit. What did you say? Implicit assumptions, or the constraints, the intent, other stuff. But also highly concurrent because git by design introduces mutexes everywhere, which sucks. So you need super concurrency. Have you seen Git Butler? Is it the guy who used to be cto. Ian, I think, is his name. I forget his name, but yeah. Scott. Scott. I think there's a lot of people.