I like knowing how the whole thing works.

Understand the system, then simplify it.

Some projects start as software and end with networking problems. Others start with hardware and suddenly need a backend, deployment or monitoring. That crossover is usually the part I enjoy most.

I care about clear boundaries, useful diagnostics and designs that can be understood later by someone who was not there when they were built.

Work that can be inspected.

When a project is public, I prefer showing the decisions and limitations as well as the finished result. Current public work spans Home Assistant dependency analysis and runtime forensics, outbound-mail tracing and Linux routing diagnostics, with source and technical documentation linked from each project page.

Code, projects and contact.

Public code lives on GitHub, with the project context collected here. LinkedIn carries the professional profile; for everything else, email is the easiest way to reach me.