>how to know what good/bad code looks like, and if it matches what you're truly asking for

And how you would know to do that, if you're not writing code?