|
|
|
|
|
by QuadmasterXLII
1277 days ago
|
|
If programming is automated but driving trucks still takes a human, someone will tell GPT-5 "Write a program that automates driving trucks". If that doesn't work, programming isn't automated. If it does, it doesn't matter that programming was the first of the jobs automated in the last 48 hours of the age of man. |
|
And, of course, it doesn't have to be at the level of producing a perfect solution for the input "Write a program that automates driving trucks". Programmers can't do that either. It's enough if it can produce usable and testable code based on user input and then it can refine the solution based on the feedback and then get to a complete solution with this method. If it can start asking questions, all the better.
BTW, ChatGPT can already do some of this without being tailored to do so. You can tell it to create a todo app (I know, that's just copypasta), defining the language and the framework to use. (I went with TS and Vue.) And then tell it to create a backend and to connect the two. Then you can tell to add persistance to the backend (because it does not, by default) and it will update the backend code. Before ChatGPT, I thought that back references like these would be the tricky thing. Sure, in my experiment I didn't talk like a non-tech person wanting an app, so you might say I was programming, but I really wasn't. And that's where things are now.
> it doesn't matter that programming was the first of the jobs automated in the last 48 hours of the age of man.
Now that's the thing I have always been unsure about. Whether automating programming is far enough from (super strong) AGI for programmers to feel bad about their job :)