James King

I like where Mike is coming from, but I can also see, like I said, some probably our listeners are yelling at the radio, Mike, you're giving away our jobs.

I mean, that's one thing that

drives me or, you know, my love for IT and AV and all that stuff is there is no one path.

Like, there's multiple ways to do things in any field.

Networking, databases, you name it, AV, there's multiple ways to do something.

Listening to Mike speak, where my mind goes is

thinking of what my boss currently keeps talking about, and that is return on effort.

Let's bring this a little bit to business.

Everyone knows the return on investment.

How much money are we gonna get back?

in whatever service we do, whatever that, but return on an effort is harder to gauge.

So like to give us a scenario, like Mike brought up, you know, code is living, breathing, always changing.

If the user just wants a simple word change on the touch panel, you know, the button change from, you know, Electron PC to

In Room PC, I don't know, just some weird things like that.

That, if that request hits the field technician, you know, and that field technician can't change it and needs to escalate it up to, say, a junior programmer.

And that junior programmer, you know, because it was locked down into this high-level code, can't do it.

So they bumped it up to the senior programmer who goes in.

That's three texts from your company to make a text change.

That's a lot of effort.

How much time and money is being spent and effort is being spent on that small change if you built it, like Mike is kind of talking about, where that field tech go, oh, you want the words changed.