Thank you so much, Scott. Yep, it's an honor to be with you and also honored to be talking in JS Tech. That's a wonder—

That's a wonderful opportunity, which we have got to have a podcast with you.

Sure. So mine basically is AI refactor, like how I upgraded from 20-year-old enterprise systems to modern JS architecture. So my background as a senior data architect, we work on a lot of automobile stuff where you have like 30 years, 40 years where they use PHP and like critical, you know, unique data connections, basically using InfoFlow or ERP system. But the main challenges right now is like most of the legacy systems are like need to be upgraded in Python or something, but the most function need to be in PHP and call and automation. That's what is required. So the whole thing running on a mission-critical operations, uh, I try to do a large-scale manufacturing ERP application, so I try to convert the classical ASP pages, VBScript, you know, all those ODBC lookups and printer-based systems. In this section, I will walk through, like, I would say I would break down our monolithic legacy applications and how I built it basically using the micro— JavaScript microservices ecosystems. So I'll be showing how I migrated from a VBScript-driven data collection flow into Node.js services and how the ERP queries into Python micro APIs. So if you have an old system you want to bring back to JavaScript or using new LLMs or Python APIs, that's what I'm going to talk about the whole thing and see about like what are the steps you have to follow, what are the sequences, what are the architecture, how AI helps to validate the logic when the production is still going on and to make it stable. That's my—

Yes, kind of like I have done a smaller application, LLM applications, like where it validates, uh, like, you know, validates logic and production stable. So basically AI is something like, you know, a developer who's helping you out just to make sure you are trying to move the architecture when you're doing most of the work.

No, we have done it in a production environment. We took almost 4 months to finish off the whole architecture. The first thing is like. You don't want to touch something which is like, you know, very, very old and the legacy systems are really old. And I don't know if you have heard about InfoFlow. It's a Unidata ERP system where most of the remanufacturing industries use. So when you're touching that and you have this ODBC queries, this legacy systems and everything. So we took like the 4 months to do it into a new language on Python APIs and LLMs was basically just to validate the logic. That's all.

Yes.

Uh, basically when you, I mean, when you're using an LLM model, you generate like human-like responses, analyze, and summarize. So my problem was like, I took like small, small parts and you needed to like, you know, validate a few things with the logic because you have a lot of test cases and everything. So it was just doing like explaining the legacy systems, what was the logic and testing it out. That's how basically.

Yeah.

And like, I mean, like most of the architecture was converted into Node.js architecture. So LLM was just like something which helps out saying like, hey, I'm there, you know, I'm just analyzing the code and just the VBScript and that's all.

Yes. I mean, my problem with using Node.js was like I needed to do a lot of backend systems and APIs, and it should be lightweight because when you're going to the production, it needs to be like migrating like from ASP to rebuilding Node.js. Validation ERP calls was like the best form for Node.js. So the endpoints handling, validation, service logics, that's what made me into, into the Node.js architecture. So we had a lot of data collection questions. I mean, basically when you're in a production line, you have like a lot of rows just coming on and you have protocols and everything. So I needed to act as a bridge between the old ERP system and the new frontend systems. So API layer, Node.js won for me.

I would say like if they know a bit of their ERP systems or legacy systems, that would be helpful for them to understand more in depth. But I will be explaining from the basics like, oh, this is this what ERP system is. So from this basics, because so many people don't know, like ERP systems, or like, uh, what you're using in the microservices or lightweight, like why are you using like Node.js instead of PHP, or are you using PHP? I am using PHP in some part of it, but not the whole thing. So I would say they would carry like how do you design, which system to select, and to really see the, you know, good example in the legacy systems and how you migrate it from a VBScript to a Node.js basically.

I would say like JS Tech has a lot of talks and you would go into the speakers and look at their talks, learn more, understand, maybe interact with them in the LinkedIn and like, you know, Go out, speak to them when you're in person, and also come to PHP Architect. I saw a lot of your podcasts and it was in-depth also. So I would always do that, both of it together.

Okay.

Yep. That, I mean, I, I was like, I was looking into that one of the talks and I saw like Nate Finch, he had decoupling with your CMS with Next.js. I was like, I want to know more about it, you know, like that. I saw it's better to reach out to people, do a network and learn even like, you know, the basics before you come out there. Yep.

Yep. Excited to meet you also in person. See you next month. Yep.