Q In order to achieve a very large refactor like you just described, do we use that same process you just saw, or is there more setup?
A I think that the workflow for, let's say, a migration is probably one of the most common. I can even give a very concrete example. Let's say you are the administrative service of a large European nation, right, like Germany or Italy, and you have a hospital system that runs on like a twenty-year-old Java code base. Now, a company wants to come in and Big four consulting firm or something like that says, we would like to transform this entire code base to Java. Um, it's gonna take X amount of time, couple months, and, you know, by the end, you'll be on a relational database, you'll be into the future, right, on Java. When that typically happens, you kind of have to almost break down what that means from a human perspective first, to then map it to how it works in our platform. You'll have a team of anywhere from four to 10 people come in, And you have a project manager who is going to work with engineers to analyze the code bases, figure out all the dependencies, map that out into docs, right? First analysis and overview of the code base. The next is a migration strategy and plan. The third is like timelines, and you're going to scope all this out. What do you do next? Well, you go to a project management tool like JIRA. And so you take those documents and a human being translates that out. We've got two epics over the next two months. This epic will have these tickets. That epi…
AI assessment note: “break down what that means from a human perspective first, to then map it”