About
Good infrastructure is the kind nobody thinks about. Servers run, logging in takes a second, a deployment goes through unattended, and an outage ends as an entry in a log, not in a calendar. Getting environments to that state and keeping them there is my job.
Day to day I move between two worlds: the classic corporate environment built on Windows Server, Active Directory and virtualisation, and container platforms with Kubernetes, GitOps and automation. Each has its own rules, and both are worth knowing well enough to tell when either is the wrong choice.
How I work
- I treat infrastructure changes like code changes: they go through a repository, they are described, and they can be reverted.
- I prefer fewer components that I understand completely over more components that work until someone touches them.
- Outages are the most valuable source of knowledge. I try to close each one with a conclusion that changes the design, not just a procedure for next time.
- Documentation is part of the deployment. An environment that cannot be handed over to another person is not finished.
Contact
The easiest way to reach me is through LinkedIn.