Steve Greenblatt

And I was going to really shift it over to James and say, Mike, one of the things he said was that the client really doesn't care if the job gets done.

You're in that seat, James.

is, or do you need to also be factored into that equation because more people, more clients are being hands-on with systems and do want to be able to maintain and, and, uh, update systems themselves?

So I also have experienced this and in our team, we had to change the way we were going about programming certain things.

And I've had situations where

somebody doesn't have the skillset to be able to edit the code that somebody else wrote.

But I also feel like it's important for us to evolve.

It's important for us to use the tools that are the best fit for the situation.

And it's important for us to embrace forward thinking technology.

So let's take this a little bit further.

Is there a rule of thumb?

Is there some way of being able to have a compromise?

Is there a best case scenario?

Sure.

So when you are approaching a project, what is the process that is used to determine?

Is there a checklist?

Is there a rubric?

Is there just one person's job to determine how this is going to be approached?

James, any insight that you want to share on that?

And what are your thoughts about how this is processed and just the scenario of knowing that there are different options and not necessarily one specific known path?