As an ancient one (graduated college 1981), my use of AI is very conservative: look things up. Generate code I can read and understand in less than 30 minutes. This is working well for me, because when the AI botches the answer, I know quickly. It either works or fails fast: there's no importable function by that name, that keyword isn't in the language, that only works in a different version of the OS. I never ask it to do something I couldn't do myself in 10x the time (spent fixing typos or missing punctuation). If I ask it to do something I don't know how to do, I create tests - usually informal - to ensure that I understand what the code is doing. If the syntax is unfamiliar, I make it explain what it's doing, and then I informally test that explanation (usually toy examples at the command line). You must learn to do these things regardless of where the answers come from - the Internet, a journal, a book, a colleague. Otherwise >>when<< it fails, you will not be able to reason about the causes for the failure and how to find a correction.

I feel like there is room for a "Slow Movement" in the age of AI/online these days.

https://en.wikipedia.org/wiki/Slow_movement_(culture)

I personally refuse to not heavily use any revolutionary technology as it comes out - the old man who says he never touches AI because it cannot be trusted is not the vision of who I want to be! Use it heavily. Understand it. Or lest be confused by its take over and success.

My experience as well (30+ years developing software for a living).

I have tried everything from generating a complete, detailed spec using AI and then one-shot generating the code, to generating code one step at a time with me reviewing each result.

The speed is pretty much the same. But generating code one step at a time is IMHO vastly superior because I deeply understand the code and can easily fix issues that the AI get stuck trying to fix.