Mike Krejci

We shouldn't be trying to just make it complicated and make it hard because we can.

And I think we get caught up in that problem, you know, in a little bit of a God complex as programmers that, you know, we can do some crazy advanced stuff and we have all of these tools to be able to do this crazy stuff.

So we should do it.

Just because you can doesn't mean you should.

Love that saying.

No, I mean, you can write this really crazy way to create this huge framework of all of these advanced level programming to do this crazy system.

But if all you need is to change three pages, there's a whole lot easier ways to do it in every one of the languages to do that that anybody can look at and figure out.

And that's where we need to get to.

There's probably a lot of parallels that we're just unaware of, right?

You know, you could even go down to think about it, how to make a cheeseburger, right?

At the end of the day, it's a bun, a ground beef, a slice of cheese.

And you've got a burger, you know, sure, you can do it a whole lot of fancier ways, but are you really improving on the original that much?

And if anything's going to probably give us, you know, come at me in the comments, it's going to be the cheeseburger comment, not taking the jobs away, James, but...

Multiple times.

A couple of years ago, there was a...

a consultant-driven design for a net new client for us at CTI, and they wanted everything to be written in Crestron.

They wanted it all written in C Sharp.

based on the system design and the, and the, uh, age of VC or, uh, C sharp, um, this was probably eight, 10 years ago.

It just did not make sense for the client.

Um, you know, and there was a, you know, a conversation with the consultant going, Hey, that's a great way we could do this.