Mike Krejci

It's out there on the job site.

We don't want customers for one project, one job, right?

That conference room, that classroom, that courtroom is going to evolve over time.

They're going to add functionality.

They're going to add equipment.

They're going to revise it.

They're going to live with the system.

So if we write that code just for that one moment in time,

When they want to come back and they want to add stuff in a couple of years, technology changes evolve.

We don't want to throw the code away and start from scratch.

That's not good for anyone.

It's not good for the customer.

It's not good for the system.

It's not good for the end user.

It's not good for the team going out to do it.

But if we can just touch a few parts of it because we left it available, oh, well, that makes it real simple.

It's really on the individual programmer.

We have a team of base code programmers in our company that write the majority of our base code, and they're writing that for all the control systems.

And the simple answer is,

Keep it simple, right?