Somehow My AI Film Turned Into a Platform
For the last seven months I’ve been building Lumarka, a platform that sits between AI video generators and actually making a movie with AI. It’s ambitious. I probably bit off more than I can chew. But the journey taught me something I didn’t expect.
I started with n8n. Built two or three dozen workflows. Got pretty good at it. But somewhere along the way I noticed something: most of my workflows were basically code with a visual wrapper. I was writing logic, handling edge cases, debugging errors… just through little boxes instead of text.
And at some point I had this very simple thought: why am I adding this extra layer at all?
With Claude Code, I can work directly with the source. No translation layer. No dragging nodes around to represent logic I could just write. When something breaks, I’m not debugging a workflow and the code inside it, I’m just debugging code. When I want to change something, I change it. The feedback loop is tighter. The power is more direct.
Don’t get me wrong, n8n still has its place. Modular automations, swapping tools in and out, quick experiments… it’s great for that. I still use it. But for building an actual product? Working directly in code with Claude as my partner is just on another level.
What really blows my mind is that I’m even able to say this. For most of my career, “code” might as well have been hieroglyphics. I avoided it. It felt like a different species of thinking. I never imagined I’d understand what was going on under the hood, let alone enjoy it.
I’m still lost sometimes. But now when I hit a wall, I have a partner who explains what’s happening in plain English, and I push through instead of bouncing off. That alone feels like a small miracle.
So what does this have to do with AI filmmaking?
At first glance this probably sounds like a nerdy tooling story. But for filmmakers, this shift is actually about something much simpler: creative control and speed.
Right now most AI filmmaking workflows are fragile. You bounce between tools, UIs, prompts, formats, and half the time you’re fighting the software instead of shaping the story. Every extra layer adds friction. Every abstraction hides what’s really happening.
What Claude Code represents to me isn’t “becoming a programmer.” It’s removing layers between an idea and the image. It’s being able to shape an end-to-end filmmaking system instead of being locked into whatever workflow a tool designer thought made sense.
And that’s the real lesson here: the future of AI filmmaking isn’t about mastering one magic app. It’s about building your own creative pipeline, one that matches how you think as a filmmaker.
You don’t need to write code to do this. But the tools are finally making it possible for non-engineers to design systems instead of just clicking buttons. That’s a massive shift.
In other words, this isn’t really a tech story.
It’s a creative power story.
The ground is shifting under all of us at the same time. Engineers and artists, coders and directors, people who've been building software for decades and people who've never touched it before.
And after all my years in post-production, I never thought I'd be excited about writing code. But here I am, waking up every day excited about what I'll create next, whether it's a film or software.
That feels like the real revolution.
5
3 comments
Lawrence Jordan
6
Somehow My AI Film Turned Into a Platform
AIography: The AI Creators Hub
From film prod to web dev. Learn how AI can assist you in bringing your creative visions to life. Join our community of creators on the cutting edge.
Leaderboard (30-day)
Powered by