Full post on my Substack

Traditional software development, prompt-driven software development. Traditionally, dev receives some requirements and then they iterate locally in their IDE until they're happy with their changes. They submit their changes for review. Either they're accepted or they go back for development. If they're accepted, then they get merged by a different dev, a different human. Prompt-driven development, same start. So dev receives some requirements and then really what they should be doing is breaking those requirements into a series of prompts. This is a new skill that developers or anyone really adopting prompt-driven development is going to have to work on is breaking requirements down into prompts that make sense. And then they enter their iteration loop that also looks a little bit different because the LLM is writing the code. So the loop looks like dev writes the prompt for the LLM, LLM writes the code, dev reviews the code that the LLM wrote, and that loop continues until all the necessary changes are made and the developer's happy with it. And then it picks right back up where we left off. Dev submits all the changes for review. If the other reviewing dev is not happy with them, kicks them back to this process. Otherwise, they just continue on and they get merged into master.