Seems I spent more time fixing it compared to thinking it myself
AI code is just bad code written by someone else that I now have to fix, and we all know the one job every coder loves is fixing code written by someone who you cannot ask: "why did you do it this way?"
Yeah, this is the way how to interact with it. It makes sense as well, because it's only predicting the next word based on the previous words, so it had can in hindsight find a lot more stuff and in general be smarter about it.
I do this with TypeScript error codes. It’s great at breaking down the problem. I never just copy paste code from it and I don’t think anyone should do that anyway.
I've had success with trivial things, like write a log file parser with this pattern, or give me a basic 3 part left-right-center header in html. Works ok for trivial side projects. I would never trust it in production. Its a tool, nothing more at this point. Like an electric drill, better than a hand crank, but you still need to know how to use it.
Yea I genuinely hope we get to the point where I don't have write code. Let me describe the architecture and algorithms with my voice in English. I'd much rather spend my time solving abstract problems than typing syntax. If I have to essentially "teach" the AI what I want by dropping down the ladder of abstraction sometimes, that's OK.
Me, with 20 years experience making software: yes, totally happy about this.
(This makes it much easier to keep up with the latest newfangled bullshit.)
Wonder if human knowledge is now going to start degrading like a reposted JPEG as AI generated information is recycled again and again into more AI systems.
And, as always, attempting to code to that spec will expose contradictions, inconsistencies, and frequently produce something that the customer judges as unfit for purpose.
Coding has never been the toughest problem, except in the matter of security attacks.