About
Systems work with practical consequences.
I'm a software engineer and systems architect based in Billings, Montana, working across enterprise software, modern web systems, data architecture, and AI-assisted engineering.
My work centers on WordPress systems, data integrations, and the kind of deep structural problems that don't show up in tutorials. I manage a fleet of 250+ active web environments, including high-stakes transactional systems for real estate APIs, cattle auction platforms, and institutional sites.
Before agency work, I was a technical lead at SunGard Higher Education, where I engineered Perl-based synthetic data generators producing over a million randomized student records for enterprise-scale performance testing. That instinct for system-level thinking has stayed with me.
I have a B.S. in Computer Science from Montana State University. I've also spent 12 years as an institutional volunteer photographer at ZooMontana, which directly informed a specialized WordPress CMS framework I built for zoological institutions.
I approach technical problems the same way regardless of scale: understand the system first, then build something that holds.
Architecture in practice
How This Website Is Built
This site is generated by a custom Python static site generator. Content lives in structured JSON, templates generate the HTML, and the finished files deploy to GitHub Pages.
There is no CMS, database, server-side application, or admin interface. The result is fast, portable, versionable, and intentionally simple to operate.
I don't choose technology first. I choose the architecture that best fits the problem.
WordPress is the right choice when clients need established editing workflows. Static generation is a better fit when dynamic infrastructure would add complexity without adding value. FYN uses static generation because privacy is architectural. Adaptive Experiences applies the same principle to preserving distinct human perspectives instead of forcing them into one generic model.
Tooling
Building the Builder
Rather than adapting my workflow to an off-the-shelf static site generator, I built the publishing system around the way I work.
Structured JSON flows through reusable templates into static HTML. The build handles navigation, page generation, article relationships, asset copying, and link validation before deployment.
That gives me a publishing system I can understand end to end, change deliberately, and keep under version control without maintaining a separate application.
Building the tooling is often part of solving the problem.
Experience