Knowing exactly what you want and having no idea how to ask for it

That’s probably been the hardest part of building with Claude Code for me. I have no engineering background, so I’d sit down knowing exactly what I wanted something to do, but have no idea what to type. The problem wasn’t that I couldn’t describe the behaviour. I just didn’t know what any of it was called. So half the time I didn’t know how to ask for what I wanted, or whether what Claude gave me was actually the right thing. I spent a lot of the first few months asking Claude what terms in its own answers actually meant, just so I could understand what it was telling me. It would explain something, I’d think “yeah, makes sense”, and then later realise I couldn’t actually explain what I’d just agreed to. That was probably the weirdest part. I knew I had huge gaps, obviously. I just couldn’t always tell where they were. When you don’t really understand what you’re looking at, a good answer and a bad answer can look pretty much the same. It’s got better, but not because I learned to code. I still can’t properly read a diff. Mostly I just stopped pretending I understood things I didn’t and started asking Claude about all the stuff I would have skipped over before. Anyone else in this spot? If you got past it, did you actually go and learn the fundamentals or did you just get better at working around what you don’t know?