Cast by leovido.eth
Show the cast this replies toI felt the same way when rebuilding /moxito I am taking a different approach where I’m focusing on prompts first and getting the foundations set for: - The app vision - The architecture - Focus on quality and CI checks and so on - Being precise on what I really want and iterate I learned that letting AI decide everything was a big mistake on my end. For a smaller app, it works well, but there are some essentials that need to come from the dev(s)
1 reply
big agree ai coding tools want to write code they want you to keep needing them and paying for credits they don't care how much complexity or bugs they add bc their motto is *don't worry i can fix it!*
They fix it but can add more bugs along the way. I let them review as much as they want but only stop and fix if it’s actually critical. Huh that makes absolute sense. They want you to keep using them unless explicitly told. Ideally I’d like a system that I own and that I built, that is not traced, tracked and does absolutely everything that I require for each project. Maybe that’s asking too much and could take months to build..?
the only way to get that kind of system is to critically review each code suggestion at that point, you're pretty close to doing actual coding w ai assistance different workflow than vibecoding without coding experience