That's so funny. I have the exact opposite experience. I find that it can quickly code well speed components if I give it criteria and feedback, but it totally falls down on architecture. I've been working as an architect for a long time though, and running teams. So maybe that's why I use it that way: like a team of fast contributors on acid.

Replies (2)

no that makes sense. i will say that it does take some time to understand how it "thinks" and to get it to understand what you're aiming for. that's part of the reason i find it better to flesh ideas and architecture out; it makes stupid mistakes or wants to take weird directions and i rein it in until we're aligned.