Comment It'll replace a lot of shovelware (Score 1) 69
I've been a game dev for 25 years, and I'm not so full of hubris to say that no LLM will ever be as good at coding as me.
But most game code isn't public domain, so there's not going to be a lot of training on it. There's a lot of weird stuff that we do at the behest of designers that nobody would ever think to do (whether that's because it's a terrible idea or a brilliant idea is really only knowable after people play the game).
The devil has always been in the details, and so much of good game development is about good human communication and understanding what makes a fun game. Sometimes you just don't know. You're 3 years into a game and there's all this tech and it still isn't fun, and you're trying to figure out the special sauce that will engage people and it's hard. And the way we usually get through it is we play a lot of games and all of us come in with our own idea of fun and we take chances based on things that we personally enjoy. Every professional designer I know plays games as homework. (Some companies help defray the cost, some just demand that they do it as a condition of their employment; it doesn't much matter, designers are gonna play games no matter what anyone tells them.)
And so I'm relatively confident that games will mostly be a collaborative effort because programmers ALSO play games and ALSO bring that experience to the table. As much as designers and programmers will complain about one another, we really do feed off of the contention. Programmers provide infrastructure, but also BOUNDARIES. We know what's slow and what's fast and what shortcuts we can take. And hey, maybe that will all be possible with an AI in the future too, but I have my doubts.
But I had Gemini fix a bunch of garbage problems with some elisp that have been plaguing me for a few years that I never would've bothered to look into because my setup was good enough. I listened to one programmer talk about how he tackled a problem of (human language) translation that he never would have attempted because the task was too large and too tedious.
I actually don't think that LLMs will be making programmers meaningfully more productive for a long while. I don't write enough so-called boilerplate code for it to save me any time there. But I'll definitely take on some tasks that never would have gotten done at all. I think we might see more small websites pop up, for instance. I've never bothered to learn anything about web dev after the HTML/Geocities/webring days, but maybe I'll do something now that LLMs can walk me through it. Small automation tasks, writing scripts. Hobbyist stuff for people that don't want another hobby.
There's already a lot of human-generated slop code out there, and maybe the folks that write that stuff are going to be replaced. I think there are really technical or esoteric or experiential programming jobs out there that won't be, though. I just have more time to do my actual work because all of the dumb little distracting tasks that I used to spend a half day on are now 10 minute LLM chats.