About

I run Linux every day and host nearly everything I use. What I build tends to start as a favour — a tool for a clan, an assistant for my family, a system for a household — and then has to keep running long after the novelty wears off.

• TroubleshootingProfessional
• DevPart-time
• AnalystFull-time

Owned, not rented

The things on this page run on hardware in my house — GPUs doing inference, containers I picked, a tunnel instead of an open port. I would rather understand a system all the way down than pay someone to keep it opaque, and self-hosting is the fastest way I know to find out which parts I only thought I understood.

Built for someone specific

None of these are portfolio pieces. The tracker bot exists because a clan needed it, the assistant because my family actually talks to it, the household system because a house is a supply chain whether or not you admit it. That constraint is the interesting part — a demo can be quietly wrong forever, but something people depend on has to survive day thirty.

The day job

Professionally I do escalated application support and analysis: following a failure across systems that were never designed to talk to each other, finding the cause rather than the first plausible story, and making sure the fix becomes something searchable so nobody has to rediscover it. The skills, rather than the stack:

• Integration troubleshooting across systems that were never meant to meet
• Root cause analysis, and data remediation in SQL
• Turning recurring incidents into documented, searchable answers
• Monitoring and alerting, so unattended work self-corrects before anyone notices
• Access and security administration on midrange platforms
• Vendor escalation — owning a problem from the user through to resolution

Currently — Not looking