Actually, I said something quite different and more general: in life, people usually take sides (from politics to sports, from science to religion, including art, literature, consoles, software). In tech, I’ve always seen people argue fiercely about anything—PlayStation vs Xbox, and even more absurd stuff (Reason vs FL Studio, Quark vs InDesign, Gemini vs ChatGPT vs Claude). That was my premise: people argue about things that are relative, that always have pros and cons, and above all are things that could easily coexist (does AI take jobs away from millions of people? That’s a problem. Will AI cure millions of people? That’s a resource. Will AI wipe out humanity? Probably—in part it already does). I just yawn and know I’ll want to understand both sides.
Second point: I probably shouldn’t say this, but it helps clarify. I’ve worked in dozens of different fields (I’ve designed hundreds of video game magazines, worked in VFX, digital engineering, music composition, and so much more). I’ve traveled a lot, taking over 500,000 photos, and I had to manually process around 4,000 or 5,000 of them—first in Lightroom, then Photoshop, then Nik, then back to Photoshop… massive workloads. Having worked for years in DaVinci, After Effects, and FL Studio when computers were incredibly slow, I can say I struggled a lot (if you’ve ever mastered a track while only being able to listen to 5 seconds at a time after a 3-minute render, and having to fix things hundreds of times—you reach level 99 patience). This is just to say: I don’t fire off an AI prompt and think, “wow, that was hard work today.”
But the issue is, I don’t just write prompts. That’s not how I work with AI—because people who do that aren’t really working with AI. First, I design: I spend days doing it, writing huge amounts of documentation by hand and doing endless preliminary research. Then I open Photoshop and create mockups—for hours, days, weeks. Once I have a clear vision, I don’t write prompts—I use a very complex AI system: one AI defines the markdown files that act as the source of truth, another plans the workflow, five to ten AIs review that plan. Here’s the interesting part: I know nothing about servers or Linux, but I rented a Linux server. I managed to install dependencies and an agent that runs in a sandbox. The agent works according to my directives, which are mediated by an AI that translates them into targeted markdown. Everything is constantly documented and monitored by me.
After working for two years on a game with GDevelop and publishing it, I learned from all the issues I encountered: even though I’m not a programmer, I wanted to “hack” GDevelop—finding a way to run it in preview on localhost reading external JS (I don’t know JavaScript), figuring out how to access the runtime and allow my AI to work externally with GDevelop and debug it. I learned an incredible amount of technical stuff I didn’t know before—but without AI, it would have been impossible. Did I work hard? Even more than when I used to do everything manually—because the amount of work has increased a hundredfold, the documents to verify have become endless—but for the first time, I can handle massive projects on my own.
Someone will say AI does everything and that I’m lazy? Honestly, who cares.