grow up
Do you remember being asked what you want to be when you grow up? The question is like an open, windy field, the scent of morning dew on the horizon in every direction. I wasn't really lost -- I had nowhere to be. In the absence of motivation, I felt it could be sensible to simply unfurl my sails and let the wind take me where it will. "I'll be an engineer, like my dad," I said, hoping to avoid further scrutiny. I didn't know what being an engineer meant. I just didn't know what to do, you know? I was like sixteen, or something. How could you know, really, what lay beyond, and if you would like it? It was but morning. I simply didn't have an answer.
In junior high, I started making paper games for my friends and some of them started to suggest I try making video games. I remember not really taking them seriously until I asked one of my friends if they really meant it as we departed from our clamorous advisory period. Me? A video game developer? I didn't know anything about how to do that.
As I explored different roles that one could have when making a video game, I finally turned to computer science in frustration. When you were just an art guy or a music guy or the design guy, no high schooler preoccupied with ACTs and SATs and AP classes actually had the commitment to work with you to make a game, even if they said they would.
Fine. I'll do it myself.
But then, it turned out that I really loved it. It was so much fun to write code, to be the progenitor of an experience that everyone could experience and enjoy forever. I quickly eclipsed my high school teacher's ability to answer my questions as I attempted to build as much as I could. It turns out that writing code was way more fun than I expected. I discovered, with delight, that when I translated my thoughts into code, the process revealed contradictions, ambiguities, and perspectives I had never considered. Writing code and making games quickly consumed my life, becoming an activity I liked even more than playing games. I found somewhere to be.
It was a lucky accident that computer science was a promising field. I gave up focusing on writing, art, and music to instead focus on code, because I just enjoyed it more. My parents happily accepted my interest, an acceptance they would not have as readily granted had I wanted to be an artist. I would likely get a well-paying job even though I ignored my studies at university to make more video games. And I did.
As I built upon my knowledge, I found myself in piles of spaghetti code wondering how it was even possible to make a game that wasn't a struggle to keep working on. It was clear to me that my code was not good and that I didn't know how to make it better. It took a long time for me to find the right people and the right books, but as I gained experience and knowledge to become a person who could make it better, I developed a much deeper appreciation for how code is designed.
Code can be utterly beautiful and at other times incredibly terrifying. It really depends on who wrote it, what they were thinking of at the time, and if you vibe with their way of thinking. For me, code does not have a smooth handle. It's not a simple, standardized tool everyone has in their toolbox. There's no "true", objectively correct answer for how to code something. Instead, code is more like a conversation with the person who wrote it, even if that person is yourself. Why did they make the code this way? How am I going to make my code work with what they made?
And when the code is compiled, the conversation persists. While admittedly most don't actually read the code and come to understand its every nook and cranny, everyone still feels the effects of how it was written. Just as you might not know every brushstroke in a painting but still appreciate the view, you will know when the game glitches or crashes, when and how the game decides to reward you, and receive answers to questions of what you can do in a game space as determined through the execution of the author's thought process.
While some may argue that code is merely the objective and formal mathematical practice of manipulating symbolic logic, to me, code is so much more and these conversations between developers and players elevates code to "art".
I feel, these days, that the "code is art" sentiment is a minority opinion. In game spaces, it's not unusual for me to come across sentiments from other developers and players who say that AI should definitely never make the visuals, the music, and the writing, but acquiesce anyhow on code and say that it's acceptable for AI-generated code to be in a game. The oft-cited reasoning being that players don't actually care about your code, as long as it works! Even in polite company that I enjoy and agree with, it's hard for me to not read this as an admission -- that it's okay to invest significant environmental harm in stealing other people's work, their thoughts, their unique expression of how they think and communicate, launder it, and then claim it as your own. It goes to reason that people think this is okay for code, because they don't think of it as art! The somewhere I want to be is becoming nothing.
In the pursuit of more beautiful code, I find with shock that it appears many are more than happy to accept Claude or some other stealing-with-extra-steps thing to just generate the code for them. It's not as if I think LLMs have no uses and that it should be barred in its entirety. In fact, if the LLMs were produced and designed in a way that aligned with my values, I'd be interested in using them myself for certain applications. I even think it's possible to make LLMs themselves in an artful way (this may be a project I might someday embark on). But for generating the code? What's the point of that, really?
If I hired a goon squad to make a game of my own specification and design, have I really made anything? If a rich person hires an artist to make a painting to their liking, has the rich person made anything? My answer is that nothing of significance was made by the commissioner. The workers did the work. The capital owner who commissioned the work, as always, feels entitled to take credit for the work as their own -- but what have they actually done?
It could be that I'm wrong. It was not long ago that LLM-generated code was truly awful. Now it gets used everywhere. Maybe it's because I live in the Bay Area, but when I go to events I see so many games that use LLM-generated code in some capacity in its development. I play the games (most of them bad, though I think this might just be because I am highly critical as this is not much of a change from when they were all entirely human-made), make friendly conversation with the developers, and ask earnest questions about what using AI is like. When I make friends with them, I get pulled into more conversations where I find people who once rejected the use of it saying, sometimes with sympathy, that we indie developers have to "grow up" and accept the LLM-generated code as the new reality. Our jobs have been made obsolete and that it would be foolish to continue without using it in some capacity. At the last event I went to, a developer commented to me in a spare moment that "of everyone in this room, I think we're the only two still writing all of the code by hand".
I know at least some people care, but it's easy to feel like no one cares about the code anymore. My love for code does not appear to be widely shared. When I listen to well-meaning developers talk about how they just can't write code themselves anymore because the LLM is so much better and faster than them, I start to think that maybe no one loved the code to begin with. It's the same as it ever was, but I just didn't get the memo.
It was after one of these conversations that I felt this existential crisis that I'm writing about. I'm sure many others have felt this as well, as "AI" touches many fields. Maybe my insistence on writing the code myself will cost me financially. Everyone knows I'm still burning cash in my backyard to try and make the dream of being an indie work, cash that I'm starting to think I'll never be able to recoup as the jobs landscape shifts as I triple down on trying to be an indie game developer.
But, I'm afraid I just can't imagine the world any other way. If I don't write the code for the art I want to make -- if I didn't speak my voice into the ether and form its expression to resemble my image in an attempt to communicate my thoughts and ideas -- someone else's image would be there instead: an echo of the average statistical likeliness, a fake simulacrum, empty and hollow. Something else is there, and that something else cares for nothing, casting a shadow that consumes and corrupts from within everything that I hold dear to my heart.