Honestly the biggest problem with #AI coding is that it lets me build things without having to think about what I want to build. It's happened twice now where the AI coded something perfectly, only for me to realize when I had exactly what I asked for, it wasn't what I needed or really wanted. I usually realize this during the act of building, and the act of building often helps me clarify what it is that I actually want.
@fastfinge You may already know this trick, but in just in case, I sometimes ask the agent to help me create a project requirements document first. I toss in what I want in terms of UI, behavior, potential platform/language/dependency info, and can find out fairly quickly, based on the result, where I've thought the idea out well enough to start coding it.
@sclower I suspect it would work better if I wrote the project requirements document myself. Then fed it into the AI for implementation. Maybe it would shift me from thinking "What do I want coded" and towards "What are my requirements". I tend to start thinking too low level, about what libraries I want to use and what language, when I still haven't one hundred percent laid out what I want to do. The example that prompted me to post was reformatting a set of files. If I'd have thought just a bit harder about what I actually needed, I would have ended up with three regular expressions and a batch script, not a C# DotNet app.
