Software Engineer · Systems Builder

I build systems that actually have to work.

Practical software, infrastructure, automation, security tooling, and AI integrations— from .NET services and WordPress platforms to cloud architecture and experimental security systems.

See what I build How I work
$ whoami
jeremy

$ cat focus.json
{
  "build": "useful software",
  "optimize": "slow systems",
  "secure": "real environments",
  "automate": "repetitive work",
  "question": "everything"
}

# currently exploring:
AI + security + infrastructure

What I build

I like projects where software touches the real world: customers, servers, networks, operations, security, and messy legacy systems.

01 / WEB SYSTEMS

Business software

Multi-tenant web apps, internal tools, APIs, dashboards, integrations, and workflow automation built around real operational needs.

02 / COMMERCE

WordPress & WooCommerce

Custom plugins, pricing systems, caching, performance analysis, search, rentals, checkout workflows, and infrastructure around high-traffic sites.

03 / INFRA

Cloud & systems

AWS, Linux, Windows Server, containers, reverse proxies, databases, deployment pipelines, observability, and the plumbing behind production systems.

04 / SECURITY

Defensive tooling

Application control, telemetry, malware analysis concepts, Windows hardening, network visibility, detection logic, and security automation.

05 / AI

AI that does work

Agents and AI-assisted systems that inspect evidence, summarize complexity, automate investigation, and connect directly to business data.

06 / R&D

Reverse engineering

Legacy protocols, unusual software behavior, performance bottlenecks, undocumented systems, and questions that require digging below the surface.

Preferred tools

I care more about understanding the system than collecting technologies, but these are the tools I reach for often.

C# / .NET ASP.NET Core PHP WordPress WooCommerce Vue JavaScript PostgreSQL MySQL Redis Docker Linux Windows AWS Nginx Grafana Loki GitHub Actions Azure DevOps PowerShell Bash
How I think

Understand the whole system, then change the smallest thing that matters.

I tend to move between application code, databases, browser behavior, operating systems, networking, infrastructure, and security because production problems rarely respect clean boundaries.

Measure first Logs, traces, captures, timings, profiles, and reproducible tests beat guessing.
Prefer simple systems Use boring technology where possible. Add complexity only when it earns its keep.
Automate repetition If a process is tedious, error-prone, or repeated, it is probably software waiting to happen.
Keep digging Undocumented behavior, weird protocols, bottlenecks, and edge cases are often the interesting part.