Steve Greenblatt

I think should be an easier task, but it certainly depends on the person.

What are some of the goals that you have moving forward?

Are you looking to be able to program your own systems and take that over or just maintain them?

Any thoughts, James?

couple of other thoughts that may or may not be valuable.

One would be to be able to have code just written as an emulator so that you can talk to a device.

And of course, it's not going to be exactly that way, but at least it gives you something to test with.

We, in my career, we spent a lot of time as independent programmers away from the system and we would write as much of our code as possible at our desk, doing as much internal testing as we could.

We would load it into a processor, but we wouldn't have any of the equipment that it would talk to.

So we kind of had to be resourceful, but of course the rubber hits the road when you load it into the system.

But I would say we were able to get at least 80% or so before we would go and test it on site.

And I'm trying to think of another thought, if you were able to get into a small system that maybe you would have used configuration and write that with Python,

maybe you could test it that way.

Obviously, you need to steal a system that is either in production or is live, but it gives you an opportunity to play with something.

But I would recommend taking a small system and writing that in Python, even if you would normally configure it, and that'll give you at least a good starting point that you could build off of.

Yeah, that makes perfect sense.

You need a solid foundation to be able to build upon, and then you start to be able to do some of the more complicated things.

But I can relate very much, Chris, to what you're saying is that it's very hard to start with a medium-sized or a large-sized project in programming.

And

And that used to be a challenge that we would have when we would try to bring somebody new to our team.