This is exactly the opposite of my experience with it.
Getting it to code, it can save me, a fairly experienced coder, quite a lot of time because it can do some boring things - boilerplate stuff, or things I can’t be bothered to look up. And I can tell if it’s done it right or not.
I’ve seen people with less coding experience use it and just take its suggestions at face value with painful results and definite detriment to their learning.
The best test I’ve seen for what it’s good at is things that are hard to do, but easy to check.
I like to use it as a jumping off point for a big project. We’re migrating from server round trip navigation to client side navigation and there’s a lot of steps to think through. It helps me get past the “blank paper” phase much faster.
I think my best experience with chatgpt is when I was digging around a typescript library without knowing the language. it was very convenient to enter type signatures and learn what they mean. I rarely am doing work like this where it’s worth opening chatgpt though.
My experience is similar. It’s a multiplier. The more capable you already are, the more you can get out of it. Perhaps not surprising in that all tools work this way.
Getting it to code, it can save me, a fairly experienced coder, quite a lot of time because it can do some boring things - boilerplate stuff, or things I can’t be bothered to look up. And I can tell if it’s done it right or not.
I’ve seen people with less coding experience use it and just take its suggestions at face value with painful results and definite detriment to their learning.
The best test I’ve seen for what it’s good at is things that are hard to do, but easy to check.