A few things
I keep coming back to.

I work with live sound for church and choir, including a choir of around twenty singers. With that many microphones, a small decision about gain, routing, compression, or effects can change what everyone hears.

I use a Behringer X32 with an S32 stage box and have worked with Yamaha mixers as well. I enjoy learning the system deeply enough to trace a routing issue, manage a livestream mix, or make the vocals clearer.

The most satisfying part is hearing everything come together in the room. It is technical work, but the purpose is the people and the music.

Armenian is my native language. It shows up throughout my life, from church and music to the software ideas I keep returning to.

MOSO grew out of organizing Armenian songs. My speech recognition work comes from wanting better tools for Armenian audio. I’m interested in technology that works well for the language as it is actually spoken and used.

I also spend time thinking about Armenian lyrics and singable translation. The wording matters, and so does whether a line fits the melody when someone sings it.

I enjoy experimenting with models locally, from language models and speech recognition to computer vision and image workflows. Running things myself makes the tradeoffs much more concrete.

My setups include an RTX 5080 desktop and an M3 Pro MacBook Pro. I work with tools such as PyTorch, Transformers, llama.cpp, and ComfyUI, and spend time on memory use, quantization, and the limits of the hardware.

I like comparing what a model promises with what I can actually get it to do in an application. That is a big part of why my projects tend to include a local interface, a deployment, or an evaluation workflow.

I also like working on practical things outside the screen. I have an Ender 3 Pro and have worked through designs for stands, hooks, docks, and small adapters.

A useful example is designing accessories around a Fanttik inflator: thinking about where the device sits, how the tube and accessories fit, and what makes the result useful in practice.

That kind of work has a familiar pattern. Start with a specific problem, make a design, check the fit, and revise it. A simple object can take more thought than it first appears.

Church media has me working across livestreams, cameras, lyric slides, thumbnails, and backgrounds. I enjoy a clear visual style that people can read quickly and that supports what is happening.

I have worked with Canon and Sony camera equipment, and I also experiment with generated imagery, video workflows, ComfyUI, and FFmpeg. Sometimes the task is creative; sometimes it is figuring out why a file is far larger than it should be.

That mix of visual judgment and technical troubleshooting is something I enjoy. It is another place where understanding the tools makes the final result better.

I’m interested in the hardware and infrastructure behind the software: Linux services, home networking, small servers, GPU memory, and getting a local application onto a machine where it can stay running.

I have worked with Ubuntu, Nginx, Gunicorn, systemd, Cloudflare, and HTTPS certificates. I also enjoy looking into practical hardware choices, including compact PCs and the tradeoffs involved in hosting a Minecraft server.

I like knowing what happens below the interface. It makes it easier to troubleshoot, choose sensible tools, and understand why something behaves differently on another machine.