Clip transcript
Let's look at, you know, um, an example harness. What if the QA reports a lot of bug tickets, and somehow magically there is an agent which parses the requirements, does a root cause analysis, pulls all the traces, pulls all the logs, puts all this in a separate work tree, does the TDD, does the, implements the fix. Because it's in your local system, you have to do test scripts, local end-to-end testing. You create a PR. You submit the PR to your team for review. And after review, you merge it into your master branch, let's say. After merging it, obviously, you have to build a Docker image, deploy it into your development environment, test it, again ship build an image to your stage environment, test it, deploy it to stage. And then you go back to the QA saying, "Here you go. You can test it now." So, I would like to ask a question in the audience, um at what points do you think the human contact is required in this, um steps 1 to 9? So, I would say the human is only required at steps 1 and 9 because the in-between steps, the agent can do a lot better work. There needs to be a human to see what work the agent is doing. And then needs to be a human at the end to validate after the work is being shipped to stage.