STEVE HENRY TECH
Document intent.
Preserve knowledge.
Build with care.
Leave a clear path.
What I Do
My work sits at the intersection of technology and the physical world. I design, build, deploy, operate, and troubleshoot systems where reliability matters and where the solution has to work outside of a drawing or a lab.
That work has taken many forms over the years, but most of it falls into four connected areas.
Broadcast & Live Production
For more than two decades, I've worked in live television and event production with systems that have to work correctly, on schedule, and often under difficult conditions.
My work includes field infrastructure, production trucks, camera and audio systems, signal distribution, remote production, and the temporary systems required to turn an empty venue into a working broadcast facility.
Fiber & Signal Infrastructure
Single-mode fiber is a major part of my work, from designing and deploying large temporary fiber plants to testing, cleaning, repairing, documenting, and troubleshooting them in the field.
I work with tactical fiber, optical transport, SDI video, audio, and data systems, with an emphasis on understanding the complete signal path rather than treating individual pieces of equipment in isolation.
Networks & Systems Integration
Modern production systems increasingly depend on networks as much as traditional video and audio infrastructure.
My experience includes production networks, managed switching, Wi-Fi, internet connectivity, remote access, redundant transport, and integrating networked equipment with traditional broadcast systems.
The goal isn't simply to make devices communicate. It's to build systems that are understandable, maintainable, and dependable.
Design, Build & Documentation
I enjoy the part of technical work where an idea becomes a physical system.
That can mean designing racks and I/O panels, rebuilding production trucks, terminating and organizing infrastructure, developing patching schemes, labeling systems, or documenting how everything connects.
Good documentation, sensible signal flow, thoughtful physical construction, and serviceability aren't finishing touches. They're part of the design.
Systems Craftsmanship
I use the term Systems Craftsmanship because it describes how I approach technical work.
A good system isn't defined only by whether it works when it is first turned on. It should be understandable. It should be maintainable. It should be possible to troubleshoot. And it should account for the people who will actually use it.
That means paying attention to details that are easy to overlook: cable routing, connectors, labeling, documentation, redundancy, physical protection, signal flow, and what happens when something fails.
The technologies change.
The responsibility to build things well doesn't.