Jamie Taylor

whatever you commit is attached to your name, regardless of whether you wrote it or not.

Right.

So, you know, just saying, Hey, but Claude wrote this or, but co-pilot wrote this.

That's not going to fly with the customers, clients, managers, whoever you're dealing with.

Right.

Oh, yeah.

So I'm using this for majority personal projects, but there are a few other projects I've been working on that are client-based where I've had permission.

That's a really important thing.

Not necessarily to ask permission, but just to say, hey, I'm going to be using this tool just so you know, but it's going through a person.

for a code review before it hits your people for code review, right?

So then everybody's aware because the last thing you want to do is say to people, yeah, cool, I've built your app and it took me 25 minutes, but also it was entirely vibe coded because they may have something to say about, well, what does the license of the code mean and all that kind of stuff, right?

I've done my own due diligence, but I always ask people to do their own due diligence as well, right?

You don't want to be caught out by that.

I just can't.

That speaks volumes to me because I don't use right-click copy-paste when I'm moving files around, even if it's on the same machine across different drives.

Yeah, exactly right.

It's always our thing because I know that I can say to it, hey, when you're done, verify everything, right?

Yep, yep, 100%, 100%.

So some of the projects that I've worked on are some of my own projects.

So I've got an open source library for ASP.NET Core that attempts to, I mentioned OWASP earlier on.