Even if you are better at or find it simpler to write code (which I often do find), that's not true for 99.xxx% of humanity. I jury startups for incubators etc now and then and this month's cohort are often using chatgpt to do the software for their startup by one of the founders who 'did a little bit of coding in uni', but is not very good. The code they produce I would write far faster and better myself without chatgpt/copilot than they do with chatgpt, but I would do it even faster and better with chatgpt/copilot.
In my experience this was the case for writing a block driver & some other low level software.
It excels and arguably outperforms in some developers in other cases; app development, CRUD, and CS labs it finds on github. There’s still a risk for bugs, but an acceptable level considering the productivity enhancement IMO.
It's all in the prompting; I use [0] and a version of [1] with some other tooling to instruct it, add my style and other context in the session and have /chatcommands that add (quite elaborate) prompts to get it to do what I want.
I use different iterations of this playground for many things I do.
[0] https://github.com/transitive-bullshit/chatgpt-api [1] https://github.com/tluyben/chatgpt-playground