honestly i've been becoming too lazy, I know exactly what I want and AI is at a point where it can turn that into code. It's good enough to a point where I start to design code around AI where it's easier for AI to understand (less DRY, less abtractions, closer to C)
I just let myself use AI on non-critical software. Personal projects and projects without deadline or high quality standards.
If it uses anything I don't know, some tech I hadn't grasped yet, I do a markdown conversation summary and make sure to include technical solutions overview. I then shove that into note software for later and, at a convenient time, use that in study mode to make sure I understand implications of whatever AI chose. I'm mostly a backend developer and this has been a great html+css primer for me.
You are treating the AI not as a tool, but as a "Material" (like wood or stone).
A master carpenter works with the grain of the wood, not against it. You are adapting your architectural style to the grain of the AI model to get the best result.
That is exactly what an Architect should do. Don't force the old rules (DRY) on a new material.
And it's probably a bad thing? Not sure yet.