Mike Krejci

But if the person at the end doesn't know how to troubleshoot it, read it, configure it, edit it, did I do anything good, right?

If they can't take that code and finish it,

then we're lost, right?

What did I do?

Sure, it was fun for me to write that.

It was easy for me to do it.

But we now just abandoned it, and now I'm the only one who can support it.

I'm the only one who can commission it.

Well, that's not a great option.

So that's really what started the conversation and the thought process is how do we determine who it's going to be, what it's going to be, how we're going to do it,

because we have such a variety of knowledge bases in our company, for sure, but in the industry, right?

You know, we're not hiring all of our programmers and commissioners and folks in the field aren't, you know, 24-year-old, you know, computer science grads who've, you know, learned all the basic, all the code languages and know that.

They're also not...

All these, you know, AV road dogs have been doing it for 30 years.

It's a mix of everybody.

I think with anything, it's a blend.

It's moderation and it's the right tool for the job.

You know, if you're dealing with complex data structures and APIs and, you know, handling JSON files, XML files, and things back and forth, you're not going to try and do that in a block-type code environment.

You're not going to try and do that...

in, you know, the pretty little tool.