As an experiment, yesterday I tried solving Day 2 (rock/paper/scissors) using ChatGPT. The initial code was pretty close, but had 3 bugs (which I listed in my tweet stream https://twitter.com/DougDonohoe/status/1599126915251834882).
I've been amazed at how quickly it spits out a solution that is 99% of the way there. This is what I do for a living. It doesn't quite scare me as most of what we do is more complicated than a well-defined programming problem. I feel like this might be another tool in the tool belt, helpful for accelerating my development time. Most of the time I know precisely what I want to do, but don't know all the best ways to do it in the language I happen to be using (e.g., Go or Scala or bash).
I wonder if programming language design can somehow be optimized for code generation by AI. But then of course you have the problem where the AI doesn't "know" the new language.
It also makes me wonder about the limits of AI code generation in less popular languages. I suspect that GPT knows a lot less about Scheme, and even less about differences among implementations, than it does about Java. Maybe an ideal "code bot" should include IRC logs in the training data.
I've been amazed at how quickly it spits out a solution that is 99% of the way there. This is what I do for a living. It doesn't quite scare me as most of what we do is more complicated than a well-defined programming problem. I feel like this might be another tool in the tool belt, helpful for accelerating my development time. Most of the time I know precisely what I want to do, but don't know all the best ways to do it in the language I happen to be using (e.g., Go or Scala or bash).