I've spent my life learning how to bring ideas to life.

I started playing music as a kid and eventually began writing and arranging it. In the 1980s I discovered the Commodore 64 and taught myself BASIC, making little programs simply because I could.

I originally entered college as a Music Education major. After working in the college computer lab, I changed direction and moved into computers and software. The two interests never really separated.

I've spent more than 30 years in software engineering, moving from databases and systems work into application development, architecture, distributed systems, cloud environments, and technical leadership.

I first encountered Microsoft Flight Simulator on a Commodore 64. Years later, after exploring the possibility of becoming a pilot, I turned back to simulation and began building my own simulated cockpit.

I didn't want flight simulation to be only a game. I wanted to use it as a way to learn. That question eventually became the seed for flight trAIner.

As a traditional software engineer, AI initially felt both exciting and unsettling. I started with simple experiments, then began using AI as a sounding board for ideas and engineering problems.

Eventually I asked a simple question: what if an AI could observe a flight simulation session and teach me what I was doing wrong? That question became the first architectural conversations around flight trAIner.

The result has been a deliberate reinvention: learning AI by building real systems rather than treating the transition as a collection of courses or certifications.