What about it makes it impossible? I’m impressed by what AI assistants can do - and in practice it doesn’t help me personally.
> Select line of code, prompt it to refactor, verify they are good, accept the changes.
It’s the “verify” part that I find tricky. Do it too fast and you spend more time debugging than you originally gained. Do it too slow and you don’t gain much time.
There is a whole category of bugs that I’m unlikely to write myself but I’m likely to overlook when reading code. Mixing up variable types, mixing up variables with similar names, misusing functions I’m unfamiliar with and more.
If I had a knife of perfect sharpness which never dulled, that would be mind-blowing. It also would very likely not make me a better cook.
This is kind of a wonky analogy though.
I might suggest that coding doesn't take as much of our time as we might think it does.
Hypothetically:
Suppose coding takes 20% of your total clock time. If you improve your coding efficiency by 10%, you've only improved your total job efficiency by 2%. This is great, but probably not the mind-blowing gain that's hyped by the AI boom.
(I used 20% as a sample here, but it's not far away from my anecdotal experience, where so much of my time is spent in spec gathering, communication, meeting security/compliance standards, etc).
I always personally thought the AI boom was more about 'what can be done automation/improvement wise for non-tech industries'
How can this be possible if you literally admit its tab completion is mindblowing?
Isn't really good tab completion good enough for at least a 5% producitvity boost? 10%? 20%?
Select line of code, prompt it to refactor, verify they are good, accept the changes