About / Behind the work

Built from
curiosity.

I’m Kyle—a father to three beautiful daughters, full-stack engineer, former audio engineer, avid snowboarder, and lifelong car enthusiast.

Family firstBuilder alwaysMountains when possible

The person everyone called when the computer stopped working.

I had a knack for technology before I knew it could become a career. When a computer, printer, network, or new piece of home technology stopped cooperating, family members often relied on me to make sense of it.

What held my attention was never only the device. I wanted to understand why it behaved the way it did, how its parts fit together, and what I could change to make it work better. A middle-school CNC programming class gave that instinct a language. A web design and development class in high school gave it a direction.

That class led to the first website I put into the world. The tools have changed dramatically since then, but the instinct has not: look closely, find the system, and make it more useful for the person depending on it.

Read the full origin story

Before software,
there was sound.

I spent part of my early career as an audio engineer at a local recording studio in Denver, recording local bands and helping turn performances into something people could carry with them.

Working with audio made technology feel creative, immediate, and deeply human. It also gave me a reason to look more seriously at programming: I wanted to build digital audio applications of my own.

I never built the audio applications I imagined. But the desire to build them helped push me toward software.

The product changed. The motivation did not. I still care about tools that disappear into the work, give people more control, and make a complicated process feel natural.

The bridge to a full-time career.

After my recording-studio experience, I enrolled at Red Rocks Community College. I had already built websites, started taking on freelance work, recorded bands, and spent years taking technology apart—sometimes literally, often figuratively—to understand it.

College and freelance development moved forward in parallel. Software development was my major, while audio engineering became my minor. That combination let me continue studying the technical side of sound while making software the center of where I wanted my career to go.

Earning my associate degree in Computer Science gave both interests a stronger foundation. It sharpened the way I thought about programming and helped carry an existing freelance path into full-time professional development.

College did not begin my development career. It went a long way toward catapulting it into a full-time profession.
See the professional trajectory

Other ways
of understanding systems.

The things I do away from a keyboard have shaped the way I work at one just as much as any framework or job title. For me, that means time in the garage and on a mountain.

Garage / Diagnostics

The garage is another kind of systems lab.

I’m an automotive enthusiast and hands-on mechanic. Cars reward the same habits that good software does: understand the whole system, read the signals, isolate the real problem, and resist replacing parts—or code—without knowing why.

That interest became the aspiration behind Axly: an iPhone OBD2 diagnostics and vehicle-knowledge platform built around live sensor data, service history, vehicle context, and practical AI.

Explore axly.pro ↗

Mountain / Snowboarding

The mountain is where I reset.

When I’m not behind a screen or under a hood, I would rather be on a snowboard. Snowboarding is where I reset—moving, adjusting, and finding a path down the mountain.

The most important part of who I am.

I’m a father to three beautiful daughters. They keep the work in perspective and remind me that the best things we build are not always products.

Software is a large part of my life, but it is not the whole of it. Family is the center. Everything else—the products, the late-night ideas, the next technical challenge—fits around that.

Different systems.
The same instinct.

A recording session, an engine, a family computer, a mountain, and a software product all ask for a version of the same thing: pay attention, understand what is happening, and respond with care.