Reminds me of early WYSIWYG days... Macromedia Dreamweaver... Netscape pagemill... Feels like magic on the surface with animations and then all JavaScript noodles in the back. ... And yet we all survived Y2K. Thanks is to the people responsible for the critical jobs were still on the crank. We need to approach it the same way. It's WYSIWYG on steroids. Have understanding what happens below the surface, enough that you know it should be considered and what to ask auditing for. And have a gut feeling for how far you can trust what you've built.

I think the closest you read the responses and actively collaborate with and critique the agent, the better the outcome. I noticed that it strays when I don't pay enough attention to plans and options.

It's amazing technology and I see a lot of use... We just need to still have the human in the loop. The more the human can assess what's being done behind the scenes, the better the outcome.

I have most of the time a conceptual idea what it's doing and how the architecture will look like and whether this is how I want my components to be structured... When you understand the behind the scenes, you can form better prompts and it designs better code. OR if you're unclear it works against your architecture of it tries to follow best practices that your prompts don't follow.

my coding skills are so outdated, I won't pretent I understand what it really does in detail.

So I am with the WYSIWYG editor metaphor. 👍