A little context
Linux at work. Rabbit holes after.
I’m a Linux systems consultant in Oslo. Work is mostly Linux, Kubernetes, and the awkward bits nobody wants to own. After hours, I follow sidequests. Sometimes they become tools or posts. Sometimes I just stay up too late.
How I work
Make it understandable. Clever can wait.
Most days I’m somewhere between Linux, Kubernetes, GitOps, secrets, and observability. A lot of it runs in PCI-DSS environments, so “probably fine” is not a deployment strategy.
I want the next person to understand what I changed and why. If the automation hides the plot, I don’t trust it.
At home I mess with my homelab, native macOS apps, local models, and coding agents. When something survives more than a weekend, I write it up.
The toolkit
Things I reach for.
01
Systems
- Linux administration, mostly RHEL
- Kubernetes with K3s and MKS
- PCI-DSS environments
- Splunk and Elastic Stack
02
Automation
- GitOps with Argo CD
- Ansible for repeatable operations
- Vault and OpenBao
- Small tools with narrow jobs
03
AI experiments
- Agentic coding workflows
- MCP servers and tool use
- Local and open models
- Fine-tuning for ops tasks