Lint

And usually these do lead you into a pit of sass for good quality code.

And if I was building for Python or TypeScript, which I have done at work a lot the past 10 years, I'd want to ship more Lint rules to catch common gotchas.

Like TypeScript, I'm continuously ratcheting up new Lint rules and stuff to try and build system guardrails to strain the system so that it sticks together, doesn't use all of the foot guns that are in TypeScript and stuff.

But Rust does a lot of this just by default with the compiler and default rules.

And so I haven't felt the need to ratchet those on just yet.

Xcode's the Apple product for building iPhone apps.

And the other engineer is like, well, how do you debug? And the first engineer was like, oh, I just use Lint.

And there was nothing wrong said anywhere in this conversation, but it was very illustrative of the fundamental gap that existed.

So then I went looking for how many iOS engineers we were employing at the time.

So I'll summarize that, but go there and if you're listening, you know, twoguystech.tv and, and read it because it goes into detail in a way that, you know, especially if you're Vibe Coding, you can just take these chunks and say, you know, here, Codex, or here, Claude Code, or, or whatever you're using, do these things when you do all the stuff, right? So, uh, you know, fundamentally the first one is make sure that you start working on...

You know, you can tell all of these AI platforms, "Hey, I want to add linting to the, you know, the, the release path." Like, when, before, before you say it's done and available to use, you know, have it go through.

Linting is, is a, is a standard function.

Like I said, it's, you don't have to necessarily have deep detail into-

If-

I don't know if it was RuboCop or if it was ESLint or something like that, but it's just like, I want this specific pattern of characters to... throw up a red flag and using a regular expression was the first way that I got into setting up those kind of automated boundaries for myself.

And just to give a clearer example of what you were talking about, a static analysis tool would be something like a Lent, like RuboCop or ESLent, which just take in a file, look at its characters, and then give you a report or a pass-fail or something like that.

as opposed to a test suite, which doesn't just look at the raw characters.

It will load and execute that code.

A practice that I've started doing is anytime I'm doing code review, if there's a comment that I'm like, I would like

to not have to leave this comment again,

I'll start thinking about, is there a way that I can turn this into a Lentra rule or some other way of catching it automatically?

Some