Mike Krejci

You know, don't try and overcomplicate things.

Don't try and make it, you know, just complicated and fancy and don't just try and show off.

What is the simplest way to program this system

that we can get it in and out of our hands as quickly and efficiently as possible, get it over to the next team, and have them successfully be able to deploy it.

And that's the methodology we use is,

It is as simple as that.

When something complicated comes across the desk, you know, then there's usually a conversation and they go, hey, I think this one might be the right one to do this with, right?

We might want to go into the...

you know, into a scripting or into a C sharp or into a Python with it, what do we think about it?

And then we talk through it, right?

We talk through, okay, do we need to move the whole program over to that?

Can we break bits and pieces of it?

Who's going to be the one to deploy it?

How are we going to support it, right?

And those are all taken into effect of, okay, great, we're going to write this in a modern language and we're going to write this in this framework.

Are you willing to support this out in the field when this ghost gets deployed?

Let's say we don't have internet on site.

You have to go out there for X amount of time to go do this to go get this up and running.

Is that something you are willing to do or not?

Does it need that?