What happens when a visionary filmmaker decides the fastest path to his next project is letting algorithms do the heavy lifting?
Neill Blomkamp—the guy who made us think deeply about class warfare in District 9—just released Nightborne, a 13-minute sci-fi short built largely with AI generation tools. It's adapted from Peter Watts' 2014 novel Echopraxia, and by most accounts, it's technically competent but narratively hollow. The kind of thing that looks impressive in a 30-second clip but collapses under any real scrutiny.
For those of us building software and shipping actual products, this should feel uncomfortably familiar.
The Technical Novelty Trap
Let's be honest: generating a coherent 13-minute visual narrative with AI is legitimately difficult. The orchestration required—consistent character models, spatial continuity, lighting coherence across scenes—represents a real technical achievement. From a pure engineering standpoint, you can see why Blomkamp was excited to experiment.
But technical achievement and artistic achievement aren't the same thing. We've seen this pattern before in software: a clever hack gets confused for a genuine solution. The "slop" criticism isn't really about the technology's competence—it's about the creative bankruptcy underneath. The AI generated what was asked, but nobody asked it to say anything worth saying.
Why Developers Should Care
This is a crucial moment for everyone shipping AI-powered tools. Blomkamp's project is a case study in what happens when you prioritize capability over purpose. He could make something fast, so he did. The business case was probably straightforward: lower production costs, faster iteration, viral marketing around the technology itself.
Sound familiar? How many of us have shipped features because the AI could do them, not because users needed them? How many dashboards have we built with LLM-generated insights that nobody actually reads?
The difference between tools that matter and tools that fade is usually this: the best ones solve specific problems for specific people. They're not impressive because they're possible—they're impressive because they're necessary. Nightborne is impressive because it's possible. That's not enough.
What This Means for the Industry
We're in a hype cycle that's starting to show cracks. The narrative was supposed to be: "AI enables creators to move faster." What we're actually seeing is: "AI enables creators to move faster toward mediocrity."
That's useful information. It suggests that the real value in AI tooling isn't going to come from replacing human judgment—it's going to come from augmenting it. The projects that'll matter five years from now probably won't be the ones that minimized human input. They'll be the ones that used AI to handle the tedious parts so humans could focus on the parts that require taste, intuition, and genuine creative vision.
For product builders, this is your permission slip to pump the brakes. Not on AI adoption—but on the assumption that faster iteration automatically means better products. It doesn't. Sometimes the constraint is the point.
Blomkamp made something technically novel that nobody needed to exist. He had the resources to make something that mattered, and he chose speed instead. That's worth thinking about the next time someone suggests your team should "just use AI" to ship something faster.
So here's the question: What's the difference between using AI as a tool to solve real problems versus using it as a shortcut around doing the hard work of knowing what problems actually matter?
Part of the **AI News in 5 Minutes* daily briefing — July 22, 2026.*
Full episode • 🎵 Spotify • ▶️ YouTube
Top comments (0)