I build technical solutions to problems that annoy me or questions I cannot stop thinking about.
My background spans software, infrastructure, embedded systems, networking, cybersecurity, and research. Different problems demand different tools.
Right now I’m especially interested in practical security, infrastructure, automation, and unusual technical problems.
A few examples from professional work.
Some details have been left out to respect the people and companies I worked with.
Built and shipped an MVP in 3 months as a solo contract developer for a small therapy practice, handling both application development and the billing/clinical workflow design, with the business owner and one clinical staff member as the primary feedback loop. Delivered working EDI integration with insurance carriers before rolling off, at which point roughly 20 clinicians were using the system. Targeted to replace software costing the practice $80K/year.
Built automation tooling as part of a 3-person team to provision and manage Azure-based training environments, serving self-paced classrooms of 15–30 users weekly and instructor-led sessions of 10–30 users roughly twice a week. Eliminated hours of manual provisioning work per session and removed a major operational bottleneck for the training team.
Designed the embedded hardware, firmware, and end-to-end data architecture for a sensor system used in assisted living environments, from board design through custom communication protocol. Replaced standard IP/access-point networking with a custom mesh protocol, improving battery life by 50% and extending device range by 30%.
A few things I’ve built.
A semantic-search experiment built around perennial philosophy.
Why? I wanted to see whether similarities across religious and philosophical texts could be explored computationally rather than discussed only in vibes.
Learned Embeddings, data pipelines, web scraping, semantic search, and the difficulty of turning philosophy into a data model.
A chess-training tool focused on identifying candidate moves.
Why? I built it because I’m bad at middlegames and wanted something more targeted than solving random tactical puzzles.
Learned Distributed processing, chess-engine analysis, queue systems, and how expensive it is to analyze a lot of positions.
A self-hosted infrastructure for experimenting with systems, networking, and automation.
Why? I built it because I wanted a place to experiment freely without worrying about breaking production systems—or paying cloud bills.
Learned Infrastructure as Code, Kubernetes, virtualization, self-hosting, and that operating systems is a skill you only really learn by running them.
A cloud-hosted honeypot that collects and visualizes intrusion attempts.
Why? I built it because I wanted to see what actually happens when an exposed system is left on the internet instead of just reading about it.
Learned Azure, Microsoft Sentinel, KQL, log analysis, and how noisy the internet really is.
A deliberately soulless web toy that generates fake rejection emails.
Why? Built partly to understand how RimWorld assembles procedural descriptions, and partly as a questionable form of exposure therapy.
Learned Procedural text generation, browser interfaces, and algorithmic comedy.
A lightweight web app for running tabletop RPG sessions.
Why? I built it because the tools I was using were either bloated, slow, or tried to do everything except the few things I actually needed.
Learned Building focused user interfaces, optimizing for simplicity, and that small tools can be more valuable than feature-rich ones.
My go to toolkit for solving problems.
The best way to reach me is by email.