Actually, I'm not here to talk about AI slop. It just happens that I've been integrating an AI agent into my daily work for a new project and I thought it might be worthwhile to share my experiences.
About me
I've been a software developer for over 40 years now. My first software class was working in Macro-11 on an old Digital PDP 11 using VT220 terminals. Things have come a long way since.
I've been wargaming on computers from the very start. My first computer war game was Grigby's War in Russia on the Atari 800.
I also always knew what I'd do when I retired: Write computer war games.
Since then I've worked on two projects, both released on Steam, with another nearing completion. My partner started working with an AI agent near the end of that last project and tried to convince me to follow. I admit I was skeptical, but agreed to give it a try on a new project.
Coding With AI
During my career I've also worked with teams as a technical coach, teaching such topics as unit testing, refactoring, patterns, SOLID concepts, etc. It's fair to say I care about the form and structure of the code. I can't turn that off. So, when I started working with AI I took it in small steps, and meticulously checked its product.
Some thoughts on basics:
- The AI's done a pretty good job of forming code on a method level. I gave it some tweaks on my preferred naming conventions, etc and it followed them thereafter.
- It's pretty good at keeping methods small, and finding repetition and extracting methods from that.
- I asked the agent to create a decorator for a class we'd created an it understood immediately what I was trying to do.
What I liked:
- My preferred way of working is to start small and build. That often means building some initial version that works, but not the way I want it and then slowly adding to it until I get to where I want. When I was doing that manually, it wouldn't be that unusual for me to forget something and then either get remindered by the compiler or by an exception when I was testing. I like that the AI understands the implications of some changes and percolates them throughout the codebase.
- I liked that I could find some tricky case and then basically type: "Write a test that confirms <case>" and there'd be a unit test created.
- The sense of progress is heady.
- The AI is great at the project configuration stuff I hate.
What I liked less:
- I had an instance where told the agent I wanted a new small feature added to a package and the solution that the AI came up with was added to the wrong class and exposed too many details it didn't have to. I had to explain how I didn't want that class to be aware of these details and nudge it to re-work the solution. To its credit, it got what I wanted immediately, but... it can make structural errors.
- Sometimes I want the AI to just do what I tell it, and sometimes I want it to review what it's going to do with me. It's a bit irritating to have to tell it to hold off execution at times. That might just be my lack of familiarity.
- I've occasionally asked the AI to produce a plan for me to review. Some of the larger scale plans have been "confused".
On A Sense of Control
Back to my need to understand the codebase. It was a basic rule of thumb on the teams I worked with that any code review looking at > 100 lines was a bad idea. We're really bad at picking out errors in large volumes of work. The point I'm trying to make is: If you want to feel as if you have some sort of connection to the codebase, keep the scope of the changes AI makes small.
I also don't trust prompts that trigger large scale changes. I experimented with AI on an existing code base and gave it a request for a major change to functionality. The change was large and the AI injected several defects, a couple of which were pretty basic.
So, my policy is: Small changes, review, add to it. For me, a work session a couple of hours in length will generate 10-20 commits.
On Quality
It used to be an article of faith that if you wanted your team to be able to move quickly with changes, you needed to keep the code "clean". Consistent naming conventions, small methods, use of patterns, etc when appropriate, keeping things simple when complexity isn't necessary. The idea was to reduce the cognitive load on developers when they had to make changes to existing code. It was also economics: Your software is likely to live for years, if not decades. You want change 100 to cost the same as change 1, if you can.
AI and game development calls all of that into question. If you have no programming background perhaps you don't care what the code looks like. If you were writing enterprise software that needs to work and be updated for a decade, that might bite you in the ass, but how many games get a v2.0?
Frankly, I see a future where code quality is less of a concern. I just hope we don't reach a day where the agent responds to a prompt with: "Who wrote this crap? I quit."
On AI and Art Assets
Here's where I perhaps get on to shaky ground.
In my experience, the relationship between war game developer and artist is "difficult". We show up with some initial asks, often for maps, counters, and perhaps some UI widgets, then we go away for a while, then come back and ask for changes. We need artists, but not for a lot of time, and not all the time. But when we need them, we need them right now.
Oh, and if we're indie war game developers, we're not made of cash.
I definitely feel for artists.
But it also feels a little weird that we won't accept AI generated art but we will accept AI generated code. Because you are going to get games that have AI generated code. That horse has left the barn and it ain't coming back.
Now put away that pitchfork. I get the aversion to ai slop. But using an AI to assist with the creation of a map, or counters? I'm not sure I would reject that out of hand.
Is it that one of the characteristics that kind of defines ai slop is "low effort"? Is it that we're reacting to the obvious lack of effort and the implied disrespect to customers? What if the product is not low effort? I don't know the answer.
In Summary
I'm committed to continuing the use of AI in our current project. I'm very interested in learning what happens with long term usage, especially when we start trying to wedge late feature requests into a larger codebase. I'll report back later.
I hope this was useful to some in this sub. I don't pretend to have all the answers so feel free to fire darts.