By Ali Moradi Dev — Film Producer & Full-Stack Developer
There's a moment on a film set when everything has to work at once. The lighting, the actors, the cameras, the sound — a hundred moving parts synchronized into a single take. If one fails, the whole scene collapses.
I didn't realize it then, but that moment was teaching me software architecture.
My Background: Two Worlds, One Mind
I'm Ali Moradi Dev — a 21-year-old from Bijar, Kurdistan Province, Iran. I worked as an assistant producer on the Iranian war film Tangeye Abu Ghorayb (The Lost Strait), a large-scale production that demanded military-level logistics, resource allocation, and real-time problem solving.
Then I taught myself to code.
And the more I learned, the more I realized: filmmaking and software engineering are the same discipline wearing different costumes.
What Film Production Taught Me About Code
- Pre-Production = System Design Before a single camera rolls, a film has a complete blueprint — shot lists, schedules, resource maps. Skipping this phase is how productions go over budget and collapse.
In software, this is architecture planning. I never open a code editor before I've mapped every database relationship, every API endpoint, every user flow on paper. Film taught me that the most expensive mistakes happen before you start, not after.
- A Scene Has One Job Every scene in a well-written film does exactly one thing — advances the plot, reveals character, or builds tension. A scene that tries to do all three usually does none well.
This maps directly to the Single Responsibility Principle. Every function, every module, every class should do one thing. When I write code that feels bloated, I ask myself: what is this scene trying to do?
- Post-Production = Refactoring The film isn't finished when shooting wraps. Post-production is where a good film becomes a great one — cutting what doesn't serve the story, tightening pacing, fixing what the edit reveals.
Refactoring is the same process. The first working version is just the rough cut. Real engineering happens in revision.
The Project: A Framework-Free E-Commerce Platform
To prove these principles, I built a complete e-commerce platform from scratch — no Laravel, no frameworks, no shortcuts.
Vanilla PHP. Raw MySQL. Handwritten JavaScript.
Why no framework?
Because frameworks are shortcuts, and shortcuts hide complexity. I wanted to understand every query, every session, every security vulnerability — not abstract it away.
The result: a full platform with secure authentication, dynamic product catalog, AJAX cart, multi-step checkout, and an admin panel with analytics.
It's open-source. You can read every line.
→ GitHub: github.com/AliDev-0/PHP-E-commerce-Platform → Product Hunt: producthunt.com/posts/php-e-commerce-platform
Building in the Margins
I'll be honest about my constraints. I'm in a small city in Iran. I don't have access to the global payment systems, cloud credits, or startup ecosystems that developers in other countries take for granted.
What I have is time, discipline, and a filmmaker's obsession with craft.
If you're building in similar conditions — limited resources, no network, no institutional support — I want you to know: the constraints are the curriculum. Every workaround I've built has taught me something a tutorial never would.
What's Next
I'm continuing to build in public. More open-source projects, more writing, more honest documentation of what it looks like to develop from the margins.
If you found this useful, follow along:
🌐 Website: alidev-0.github.io
💻 GitHub: github.com/AliDev-0
🎬 IMDb: imdb.com/name/nm17111758
📝 Medium: alidev-0.medium.com
💼 LinkedIn: linkedin.com/in/alimoradidev
📸 Instagram: @alidev_0
🎥 YouTube: @AliDev_0
Ali Moradi Dev is an Iranian film producer and full-stack developer building at the intersection of cinema and software. Born January 26, 2005, in Bijar, Kurdistan Province, Iran.
