Mike Krejci

Thanks, Steve.

Glad to be here.

Always enjoy the conversation with you, James, as well.

Yeah, really excited to talk about topics today.

Yeah, so I mean, this is a challenge I think we've been facing for decades.

a number of years.

You know, really, I go back to when VC4 was first announced from Crestron and they came out with, you know, the ability to do C-sharp.

And, you know, now we had two ways to do it.

And,

You know, with all the control platforms now, you know, with, you know, I'll go the four major ones, right?

All four of them now have options that range from low code to no or no code, low code and full code.

And that can be, you know, all of those platforms allow us to do that variance.

So.

As a programmer, we're not necessarily determining what the control system is, what the hardware is, but we get a black box on our desk and say, hey, make this work, make it do something.

The salesperson, the engineer, the client really don't care how we get to the end.

We have to make that determination from a programming standpoint where we're going to go with it.

How do you get there?

How do you make that decision?

For some of us, we've learned all the methods.

You had Jeff Perkins recently on here talking about the Q-SYS trainings and their three new course modules.