Most conversations I see are about things like Replit, v0, or Cursor helping generate code faster. That’s obviously useful for getting prototypes running quickly. But what I kept running into was that the messy part wasn’t always writing code, it was figuring out what the product actually needed to do before development started. I’ve been experimenting with a mix of tools for that earlier stage as well, things like Artus, Bolt, and Durable alongside the usual builders. What’s interesting is how much clarity you get when user flows, feature scope, and system structure are mapped before you start generating code. It doesn’t remove the need for engineering judgment, but it does seem to reduce the “figure it out halfway through the build” problem. Curious if anyone else is approaching MVPs this way, planning and structuring first, then generating and building after. submitted by /u/Tough_Reward3739
Originally posted by u/Tough_Reward3739 on r/ArtificialInteligence