Treat your first build like a rough draft. Speed through it, then spend most of your time editing and rebuilding based on what you learn. AI can help you iterate faster by generating ideas and code changes through prompts.
Spend more time editing than writing. My ongoing line about no-code and like other tools that accelerate development is how it really accelerates redevelopment because there are a lot of lessons you get particularly on the business side in the first build, and then you're able to go build this again. The, the key to this though, is having an editorial mindset saying that you're not trying to do the first version perfectly, you're going to move fast on that, figure out what was wrong with that, and then go build again. That really is where the edit process comes in. I find And this works really well, especially with AI, where it can start to give you ideas, you start to dial things in, both through direct interaction with the code or with the tool, but also with the prompt, you get to figure out which of those two things is going to make the most sense for you. So my recommendation is when you are thinking about how you should be spending your time, think of it like an editor, you're spending more time in the breach, more time figuring out issues, more time doing the rebuild than doing the initial build, and you'll be more successful.
