Where it started
Back in 2020, my entire creative world was framed through a viewfinder. I was editing slideshow videos and learning the basics of pacing, color, and rhythm — long before I ever opened a code editor. I didn't know it then, but those years behind the camera were quietly teaching me principles I'd later lean on as a software engineer.
The first crossover
By 2023, I had directed music videos and produced commercial content for real clients. Around the same time, I started experimenting with web development — first as demo projects, then as production-ready applications. The two disciplines felt worlds apart at first. One was visual storytelling under deadline pressure; the other was logic, structure, and systems thinking.
It didn't take long to notice the overlap.
What carried over
A good shot has one job. A good UI component has one job too.
A few specific habits crossed over directly:
- Pacing — knowing when a scene (or a page) needs to breathe versus move fast
- Visual hierarchy — directing the eye to what matters most, whether it's a hero shot or a call-to-action button
- Iteration under constraints — shipping with limited time, limited budget, and limited gear (or limited dev hours)
- Client communication — translating a vague creative brief into something concrete, whether that's a final cut or a working feature
Where I am now
Today I split my time between directing and editing visual content and building full-stack platforms — e-commerce sites, business websites, and now this very portfolio. I don't think of myself as a developer who also does video, or a videographer who also codes. They're the same skill, applied to different mediums: understanding what someone needs to feel when they interact with something, and engineering that feeling deliberately.
If you're early in a similar dual path, my advice is simple: don't treat your other skills as a distraction from "the real work." They're training data for taste — and taste is what separates functional from memorable.