Engineering
Architecture rationale, implementation choices, and maintainability decisions under real product constraints.
One Practice Across Systems and Stories
I am Alden Gillespy. I build software systems and produce visual stories. The tools change between code and camera, but the method stays the same: define intent, work inside constraints, and execute with discipline.
Who I Am
My work combines software engineering and visual production. On one project I may be modeling data, structuring routes, and making architecture decisions. On another, I may be planning coverage, directing a sequence, and shaping rhythm in the edit.
What connects those environments is responsibility. I care about taking ideas from vague to concrete, making key decisions explicit, and shipping work that remains understandable to collaborators after the first handoff.
A Multidisciplinary Practice, Not Two Separate Careers
Engineering and production can look unrelated from the outside, but I do not treat them as parallel tracks. They are two views into the same working style.
Engineering is where I show system clarity: boundaries, naming, tradeoffs, and long-term maintainability. Production is where I show narrative clarity: framing, coverage strategy, pacing, and editorial intent.
Both require the same judgment: choose what matters, remove what does not, and leave behind structure that supports the next decision.
How I Think About the Work
Across engineering and production, my process follows a repeatable decision model.
Start from audience and outcome
Before choosing frameworks or shot lists, I define who the work is for and what should change for them by the end.
Make tradeoffs legible
I document why decisions were made, from architecture constraints to editorial choices, so teams can reason about the work instead of guessing.
Design for revision
I structure code and coverage so iteration stays possible when scope, timelines, or requirements shift.
Use restraint as a craft tool
I avoid unnecessary abstraction, unnecessary effects, and unnecessary complexity. Clarity is usually a stronger signal than novelty.
Why the Site Is Split Into Engineering and Production
The split is intentional. Each section lets you evaluate a different kind of evidence from the same practice.
Production
Story intent, visual strategy, and editorial control from capture through final cut.
They belong on one site because they reinforce each other. Engineering sharpens how I structure complex problems. Production sharpens how I control attention, sequence, and emotional clarity. Together they produce work that is both functional and authored.
Choose the lens that matches your question.
If you want technical depth, start with engineering case studies. If you want narrative and visual execution, start with production case studies. For role context across both, review the resume.