I mean, it is something I think I want to start bringing to my projects. I was trying to think about how beginner friendly it is because most of the people on my team are still newer to Elixir. They kind of like live view because they're used to writing lots of JavaScript and so it's making things easier, but they have to change their mindset. They have to wrap their head around, oh, what is this socket of signs and what I have to use as a sign stuff? And then they're not used to, you know, last thing it's a good to value way to will be returned, right? And also one of the other things I keep trip to trip up on is like, if you assign something, they think that the socket was being mutated, but actually it's been transformed. There's another thing you have to kind of what I call catch. You have to bind that to the variable and then return it at the end, right? So if you don't bind to the socket, I think it's returned when you assign, then you're going to miss the assigns. So there's a lot of these kind of things. And so I just wonder if bringing this into the mix, sure, it'll help to code quality, but will they actually understand it? Will it be something that they can be like, okay, I

can, okay, I see how I can make this better. That's what I kind of worry about. Maybe I'll try it out and also see like what Keto actually tells you then because like I said, it gives you opportunity to ask it. Okay, why do you give me this warning? And then it has put my experience a pretty decent explanation of like, okay, this is an issue because this is that one thing I also like I think didn't mention yet is that by default, it runs a certain set of checks, but it has like a whole bunch of checks. But you can also generate a configuration file, which is basically equivalent then to the default. And like a nice thing in there is all the checks are listed, like everything. So like there's basically a big list of checks Keto has. And it's not like an opt out thing, like literally need to opt in to do a certain check. So you're not like an upper-interest where you say, hey, please don't do this check. But rather in Keto, you say, okay, please do this check. And to do this, able to check you comment it out of the list or you remove it from the list. So it's very configurable by default. All of the checks are following a certain behavior. So if you're in your team, actually say, okay, we have a very specific style thing we would like to enforce. You can write your own check, like I'm going to stop it. So from doing that. And all of the checks in Keto are built around this, this, this interface. It's behavior.