Automation & Custom Tools
Small scripts, utilities, and applications that eliminate repetitive work and solve specific problems.
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.
I enjoy solving technical problems, whether that's building something new, fixing something old, or figuring out why something refuses to work in the first place.
From cloud infrastructure and automation to custom tools and everyday IT headaches, I prefer practical solutions over buzzwords. If the job is too small for a consulting firm, or you just need someone to finally fix the printer, I'd be happy to take a look.
Small scripts, utilities, and applications that eliminate repetitive work and solve specific problems.
Linux, Windows, networking, virtualization, cloud, self-hosting, and keeping systems running reliably.
Troubleshooting, research, and tackling the kinds of technical problems that don't come with a straightforward answer.
A few examples from professional work.
Some details have been left out to respect the people and companies I worked with.
Designed and implemented a web-based electronic health record system for therapists, including patient management, billing integration, and hosting infrastructure. Worked across the full stack from application development to deployment and healthcare data compliance.
Built tooling to automate the provisioning and management of Azure-based training environments, enabling self-paced learners to access cloud labs without exposing internal Azure resources. Also supported students and improved classroom deployment workflows.
Designed embedded hardware and firmware for sensor systems used in assisted living environments, while also contributing to supporting infrastructure, compliance, and office IT. Developed custom communication protocols that significantly improved battery life and device range.
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.