Steve Greenblatt

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.

We said, we don't really get easy projects because people don't hire us for those.

So if you get an opportunity to do an easy project, take advantage of it.

And plus also with the road that you're going down, being able to have more influence over the design that can really benefit you as well.

The nice part about that too, is once you have something that you know works, you can then use it for the next project as well.

So it's, you know, start to build your library.

Great segue there.

Something that we wanted to touch on.

And honestly, use your background too.

You do have a different approach than many of us coming from your social work background and being personable and having those people skills.

That goes a long way, especially, and it's different from many of the people that are very, very technical.