Yes, in the next couple of years. Right now it's a bit like supervising a bright but overconfident kid. It does a good job on some things, but often introduces new mistakes in the process of correcting earlier ones.
For example, I might ask it write a function and get one that's mostly right, except for one thing. I'll tell it 'great, just change_one_thing' and it will rewrite the function function differently (switching a structure from a tuple to a dictionary, or adding in calls to functions that don't exist etc.).
It helps a lot to start with an outline and use consistent labels in instructions. Also, to bear in mind that it will almost invariably charge ahead with its best guess rather than asking a clarifying question.
I'm seriously considering switching to a career that goes beyond scripting. Might try some low level work that requires good understanding of computer internals. Does it make sense? I now work as a DE and my work is 100% of scripts.
I can't say for sure, but it seems like there's a big market for internet-of-things developers, and working on small-capacity systems with limited computer resources definitely demands such understanding. It's cheap to try out, since microcontrollers with a usb interface can be bought for just a few dollars, and the development tools like Arduino IDE or VS code plugins are reasonably mature. IT's also fun to work on tiny computers, without being difficult to get started.
Don't let that deter you. There is usually more demand than supply and in the microcontroller market I think that will go on for quite a while, because uCs are so cheap that every manufacturer wants to put one in a consumer device. If you keep having fun and make cool little projects you can carry in your pocket and show to people, sooner or later someone will ask you to do it in exchange for money. It's one of the nice things about the technology industry.
For example, I might ask it write a function and get one that's mostly right, except for one thing. I'll tell it 'great, just change_one_thing' and it will rewrite the function function differently (switching a structure from a tuple to a dictionary, or adding in calls to functions that don't exist etc.).
It helps a lot to start with an outline and use consistent labels in instructions. Also, to bear in mind that it will almost invariably charge ahead with its best guess rather than asking a clarifying question.