About Me
Hey, I’m Joey. I'm a network and systems engineer based in Fletcher, North Carolina, currently working at Biltmore Church. Most of what I do lives behind the scenes: building, supporting, and troubleshooting the infrastructure that keeps production environments running smoothly. The goal is pretty simple: when people walk into a room to lead, produce, stream, or communicate, the technology should just work.
What I Do
My work sits somewhere between networking, live production, AV systems, and custom software. I spend a lot of time thinking through routing, reliability, signal flow, control systems, and all the little pieces that have to talk to each other without becoming a problem. And when the off-the-shelf tools do not quite solve the issue, I usually end up building something myself, whether that is a Swift app, a browser-based tool, or some other custom workflow that makes the system easier to use.
How I Got Here
Before all of this, I studied graphic design. That background still shapes the way I approach engineering. I care a lot about clean interfaces, simple workflows, and systems that make sense to the people actually using them. Over time, I realized I was just as interested, maybe more interested, in the infrastructure behind the content as I was in the content itself. That is what pulled me deeper into networked AV, broadcast systems, and the wild world of making complex technology feel simple.
How I Think About Engineering
My approach to engineering is shaped by the belief that technology exists to serve people. The best systems are often the ones nobody notices because they’re quietly helping teams communicate, collaborate, and do their best work. Often times the technology behind the scenes has to be complicated. That’s okay. But the experience for the people using it shouldn’t be. I’m not interested in building complex systems just because they look impressive. I care about building reliable, practical infrastructure that stays out of the way and helps people succeed. That philosophy extends beyond technology. Some of the most important lessons I’ve learned about teamwork, trust, and community actually came from ice hockey. I recently wrote down some of those ideas in an article called My Thoughts on Hockey.
Outside of Work
When I am not working on systems, I am probably hiking, spending time with my dog, building some random tool because I got tired of doing something manually, or watching hockey and baseball — usually cheering for the Montreal Canadiens and the Atlanta Braves. I have a habit of turning small annoyances into side projects, which is probably why so much of my work ends up living somewhere between problem-solving, design, and “there has to be a better way to do this.”