Johnathon Claudius

So like basically every programming language has, you know, either a blast or a third party sort of tooling that they call linting.

And all it does is it makes sure that you conform to the conventions of that particular language well.

So example would be like in Go, if you run an action and it has the potential to error, you always equal that error and then you have to check that error, right?

So if you're not doing those things, there's a good chance that you could run an operation, not check the error and continue on with like depositing funds into someone's wallet or something like that.

So like these simple things, they go a long way to just sort of like improve code hygiene.

And if code hygiene is better, generally speaking, a lot of other things just become easier.

And it's a, I would say some folks roll their eyes at linting, but I personally find that it's actually quite valuable to like be strongly automatic to the language that you're writing in.

Yeah, yeah, definitely.

Yeah, I think it's an interesting question.

It probably depends a lot on the specific project risk in and of itself.

Like, I think what a lot of folks...

assume is that there is a there's a one size fits all policy here.

And the reality is that there isn't a lot of times you need to be thinking about like what's the threat model for the project itself.

For example, like if I have a pet project that is like my own personal finance app, yeah, I'm going to vibe code the whole thing and eat it to whatever, right?

It's just for my own personal use.

But for the sake of other projects, it really just depends on some of the decisions that they're making inside the project and what are the risk parameters.

I think for a lot of projects that we work with, their goal is to ship fast and our goal is to help them do that.

But the only way that you can ship fast is that if you feel reasonably confident that making a mistake along the way is not going to cost you millions and millions of dollars.

So the sort of like the fundamental principle that we're trying to bake into these long-term engagements that we work with clients is a sense of defense in depth, right?

So if I told you that I'd be willing to ship code, you know, maybe once a week or even live, if I knew that there was some sort of risk system or there was like an in-protocol variant that would always be respected, meaning that like maybe I can't ever spend more than $100,000 in the wrong direction in any given day.