About
I’m a systems engineer by origin and a platform engineer by direction. I care about infrastructure that is boring to operate: reviewed, repeatable, observable and secure by default.
Professional focus
My work covers the path from a commit to a running, monitored service, and the foundations under it: Linux systems, CI/CD, container platforms, Kubernetes, identity and access, secrets and observability.
I started out running Linux servers and networks. Repetitive operations led to automation; automation led to delivery pipelines and containers; and running those for multiple teams led to platform engineering, where the goal is to give other engineers a safe, well-paved path to production.
Engineering philosophy
- Automate the second time
- A task done by hand once is learning. Done twice, it becomes a script; done by others, a tool.
- Git is the source of truth
- Infrastructure, cluster state and access rules live in version control, so every change has a diff, a reviewer and a way back.
- Secure by default
- The easy path should be the safe one. Security that depends on people remembering is not security.
- Observable before it is critical
- If you cannot see a system working, you will not see it failing. Monitoring ships with the service, not after the first incident.
- Repeatable over clever
- A boring procedure anyone on the team can run beats an elegant one only its author understands.
- Clear ownership
- Every system, alert and exception has a named owner. Shared responsibility without an owner is nobody’s responsibility.
Ownership and leadership
Much of the work is technical ownership: deciding how a platform should be built, writing the standards other teams follow, and being accountable for the systems once they run.
In practice that means making and documenting architecture decisions, standardizing delivery and access patterns across teams, coordinating migrations onto shared tooling, reviewing infrastructure changes, and helping engineers get comfortable with Linux, containers and Kubernetes.
Community
Teaching and contributing to the regional network and systems community.
Led the Systems and Services workshop at SomNOG 9
SomNOG 9 Workshops and Conference: “Connected by Design: Advancing Somalia’s Digital Infrastructure and Integrated Public Services”
Led the three-day, hands-on Systems and Services workshop for the first time, training technical staff to configure and operate Internet services on Linux. Coordinated the instructor team to deliver the track and received a certificate of appreciation from SomNOG.
Toolbox
Grouped by what the tools are for, with where they show up in my work.
Linux & systems
Building, hardening, patching and troubleshooting Linux servers; the foundation everything else runs on.
RHEL-family Linux, Ubuntu, systemd, SSH, LVM, SELinux
Containers & Kubernetes
Packaging services as images and operating on-premises Kubernetes clusters, including upgrades, policy and add-ons.
Docker, RKE2, k3s, Kubernetes, Helm, Kustomize
CI/CD & GitOps
Designing shared pipelines and promotion flows, and reconciling cluster state from Git.
GitLab CI, Argo CD, Flux, container registries
See: Standardizing application delivery with GitLab CI; A Kubernetes platform operated through GitOps
Infrastructure as code & automation
Describing infrastructure and configuration as reviewed code so environments are repeatable.
Terraform, Ansible, Bash, Python
Security, identity & access
Central identity, scoped access, secrets out of repositories, and scanning built into delivery.
FreeIPA, Kerberos, SSSD, HashiCorp Vault, Trivy
See: Centralized Linux identity and privileged access; Secrets management with Vault
Observability
Metrics, logs and alerting with ownership, so problems are found by alerts rather than users.
Prometheus, Grafana, Loki, Alertmanager
Networking
Enough depth to design and debug how traffic reaches services, from DNS and TLS to ingress and network policy.
DNS, TLS, load balancing, Ingress NGINX, network policies
Certifications
Useful structure for learning; production experience is in the case studies.
- DCADocker Certified Associate
- KCNAKubernetes and Cloud Native Associate
- LPIC-1LPIC-1 Linux Administrator
Current direction
I’m moving further toward platform engineering and large-scale digital infrastructure: internal developer platforms, identity, and data exchange systems where reliability and security matter at a public scale.