IT engineer · sysadmin · professional overthinker

I make machines behave. Usually.

Ich baue Infrastruktur aus Neugier, automatisiere aus Prinzip und debugge Dinge, die laut Dokumentation gar nicht kaputt sein können.

Live-ish view of curiosity.service

LINUX◆DOCKER◆NETWORKS◆PYTHON◆SELF-HOSTING◆TOO MUCH COFFEE◆

The operating manual

I don’t collect tech for the spec sheet. I build systems to understand how they fail — and how to make them calm, useful and a little bit delightful.

Things currently humming

A small digital ecosystem.
Entirely reasonable.

Home lab

Ten VMs.
Zero chill.

3.5TB

NAS storage for important data, questionable backups and files named final_v2_really_final.

Automation with opinions.

~30

Docker containers, each definitely essential.

The process

Observe.
Break.
Understand.

Production is just a lab with better monitoring.

01

Find the odd thing.

The weird edge case is usually where the interesting work begins.

02

Make it visible.

Logs, metrics and diagrams. If a system can’t explain itself, it isn’t finished.

03

Remove the boring part.

Good automation is quiet. It gives people their attention back.

“It’s not a bug.
It’s an undocumented feature.”

— every incident review, eventually

Open connection

Found something
interesting?

[email protected]

Root access granted

You found the quiet part.

uptime: longer than expected
coffee: ∞
confidence: unverified
curiosity: 100%

There are no points. Just the deep satisfaction of pressing suspicious buttons.