Grant Harvey

And the ability to spend an hour and a half or two hours, whatever the case is, and do this little thing

yourself for what you need or what your department or team really needs and you need it urgently.

It seems like a really powerful thing.

And you can do it in less time than it takes to fill out the ticket and wait for the first response.

You've still got a human at each end, yeah.

Yeah, I think that's fair.

And it might be that, you know, the truth is when you look across a team and the different departments and the different

needs of different teams doing very wildly different tasks.

You know, there's probably not a single tool approach that's ever going to work for anybody.

You're probably going to need to have a toolbox.

Somebody needs access to whatever, or we need to revoke access to, yeah, there's a little tab.

So I have kind of a two-part question here.

Does that leave us creating some kind of technical debt, maybe, of sorts?

And what's the scariest thing that could go wrong when you democratize this type of building?

That's smart.

I feel like, you know, having a base understanding of some things like, like, you know, what would you, what's the bare minimum you'd really want someone to know?

Like, you know, you should probably understand versioning a little bit, you know, some, some things like that, you know, as far as being able to walk back changes and stuff would be really helpful for folks.

That's so crazy.

So answer me this.

When we're talking about average people building software, do you feel like the biggest impact for this will be in internal tools or that there will be customer facing solutions?