THE THROUGH-LINE
Curiosity turned into a career. The career turned into a deeper engineering path.
I started in information technology in 1998 and grew through support, networking, systems administration, enterprise migrations, consulting, infrastructure architecture, field engineering, cloud, security, automation, and technical leadership. Working across those layers taught me that the hardest problems rarely belong to a single product. They live in the relationships between systems, people, processes, failure modes, and constraints.
That is why my work now crosses disciplines. I write Python and PowerShell because infrastructure should be automatable. I study software because operational systems increasingly are software. I study mathematics and physics because advanced computing rests on both. I explore AI, distributed systems, HPC, robotics, and quantum technologies because the next generation of computing will require people who can reason across hardware, software, infrastructure, and scientific models rather than treating them as isolated specialties.
I also build outside traditional infrastructure: interactive learning systems, scientific visualizations, AI experiments, automation tools, games, and browser labs. Building is how I test whether I actually understand something. If an idea cannot survive contact with implementation, debugging, measurement, and another person trying to use it, the understanding is not finished.
