Grant Harvey

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?

So what would your advice be to say engineering leaders right now who might be looking at this kind of stuff as a threat?

Awesome.

The ability to recognize those kind of shortcomings is big too, I think.

And understand how to quickly go learn something, whether that's a Coursera course or hopping into ChatGPT, for example, and being like, hey, run me through this, talk me through it till I get it.

And, you know, operating in a lifetime of little micro lessons, for lack of a better way to put it.

I think that's a good idea.

We always have a couple of little quick fires here.

Nice.

What's one feature you wish AI could handle but still can't?