> In engineering I treat it like a junior intern that is very fast, has memorized a huge amount of info, but makes mistakes and has to be hand-held and anything they produce must be examined and tested

So you spend your own experienced dev time chasing down a high volume of junior dev mistakes instead of writing high quality experienced dev code?

Sorting through large amounts of junior intern code does not seem like a valuable use of an experienced dev's time.

I use it where it saves time and don't use it where it doesn't, and have learned over time where those places tend to be. As AI gets better it'll get useful in more places.

Like any dev tool you have to play with it.