I've been coding since the 1980s, full-time since the mid 90s. Anyone NOT using some degree of AI at this point is really a luddite in that regard.
Not using at least some AI is along the lines of saying that IDEs make bad programmers, or inline auto-complete makes for bad programmers, etc. There has to be some kind of underlying dogma to not be using it at all at this point.
And this comes from someone whose code was originally stored on cassette tapes, and was thrilled to death having two floppy drives on my Amiga (one for the compiler, linker, header files and linker libraries, and the other for my source code and build folder - man that was state of the art with multiple UI windows going with my code, shell, etc all at once!).
There is a proper way to use AI in most any context. I've used it across the spectrum, from just chatting with an LLM to get documentation, function reference and very small, concise bits of code, to fully integrated IDE vibe-style coding. There is a proper way to use it to enhance your efficiency and improve your code.
For me personally, it is primarily an assistant I have doing very specific things to save me time and mental fatigue. Especially generating HTML and CSS. Man do I hate that entire realm (and I was one of a small group of students who created the very first web page for ysu.edu).
Examples...
I have a microcontroller capturing data from my backyard weather station and uploading to my web server every 30 seconds. I wanted a webpage to display my weather data, including graphing, but didn't want to screw around for hours tweaking HTML, CSS and JS to make it look like I wanted. So I vibe coded it. Done.
I have an Android app implemented in Java that's a Kiosk style app that displays lots of information used on a Cable TV channel. Android was a bad platform for this to run on 24/7, so I wanted to totally re-implement it. I used AI to help me choose a UI framework (this software is not for distribution), so I went with Qt. Then I used AI extensively to rewrite the code. Now, I did not have it do any kind of actual porting from Android Java to Qt C++, but I used it for examples and to learn Qt faster. I estimate this at least reduced the time I spent on this project by 1/3. At least. I had it done within a week, which is pretty amazing really, given the size and complexity of this project, and I knew NOTHING about Qt at the start. With the Android box we had to have it reboot nightly to have any degree of stability. Now it's ran for hundreds of days non-stop with zero issues on a RPi 5. It was simply like having a Qt expert on hand to answer any specific question I had and give code examples to match what I was trying to achieve.
I could go on and on. It's just a matter of choosing the right way to use AI for the project. In my main gig, which has a repository several gigabytes of code, I use it like a focused laser beam or scalpel to make whatever I do more efficient (when needed). For other projects where I just need some one-off thing, I'll use AI more extensively to generate bulk code. Then I whip the result into shape and architect it to make more sense for maintainability and future expansion.