Well I didn't say you should never concern yourself with the details.
But at some point in your life you will have gone through the details so often you won't be getting them wrong, but you'll still be spending a lot of time on them. With a tool like cgpt you can save yourself a lot of time.
Of course it's up to you where you take the trade. If your thing is a medical device that will kill someone if it isn't checked, maybe you carefully write the code yourself. If you're building some POC website, why not let the AI fill in a few API calls for you?
And don't forget, plenty of details are already outsourced. Entire reference books are full of details that we prefer not to keep memorized.
Plato:
“If men learn this, it will implant forgetfulness in their souls; they will cease to exercise memory because they rely on that which is written, calling things to remembrance no longer from within themselves, but by means of external marks. What you have discovered is a recipe not for memory, but for reminder. And it is no true wisdom that you offer your disciples, but only its semblance, for by telling them of many things without teaching them you will make them seem to know much, while for the most part they know nothing, and as men filled, not with wisdom, but with the conceit of wisdom, they will be a burden to their fellows.”
https://www.goodreads.com/quotes/259062-if-men-learn-this-it...
I'm advocating cgpt as a tool that allows you to spend more time at the level of abstraction that is appropriate for the problem. If you're writing an essay about the fall of Rome, you don't want to be spending loads of time finding the details of a reference (year published, secondary author's names, exact title...). You want to be talking about economics of the time, incentives for different groups in Roman society, and so on.