People assume development and video editing are opposite talents — one logical, one creative. After doing both professionally for years, I can tell you they are the same job wearing different clothes. Writing code made my edits sharper, and cutting video made my interfaces better. This is what each craft taught the other.
Timing is everything in both
An easing curve in CSS and an easing curve in the After Effects graph editor are literally the same math, and both decide whether something feels cheap or premium. Editing taught me to feel rhythm in frames, and that sense now drives every interaction I build — how long a hover state lingers, how a page reveals on scroll, when to hold back instead of animating everything. Developers who have never cut video tend to animate too much. Editors who have never shipped code tend to ignore the cost of every millisecond.
Systems beat one-offs
In code I reach for components, design tokens, and auto-layout. In video I reach for presets, text animators, and Motion Graphics templates. Both are the same instinct: build the pattern once, reuse it everywhere, change it in one place. The [BeeSim Support](/projects/beesim-support) portal runs on ticket categories and assignment rules for the same reason my edits run on animator presets — a system scales, a one-off does not.
Iteration is the actual skill
Neither craft rewards getting it right the first time. Code goes through drafts, reviews, and refactors. Edits go through rough cuts, client notes, and version twelve. Working in both taught me to detach from any single version and to treat feedback as data instead of criticism. The willingness to cut a beloved transition is the same muscle as deleting a clever function that nobody can maintain.
Constraints make both better
A sixty-second vertical reel and a performance budget are the same kind of gift. Both force clarity: one message per section, nothing decorative, every element earning its place. Some of my cleanest code and my tightest edits came from the smallest briefs. Unlimited time and unlimited scope have never once improved my work.
Where they meet
My [portfolio site](/projects/suffixs-portfolio) is where both crafts finally share one screen — a Next.js build with motion-design instincts, parallax depth, and scroll-triggered reveals timed like cuts. If you hire one person who does both, you do not get two half-skills. You get someone who thinks in timing and ships in systems.