About

I like systems that can explain themselves.

I’m Aland. I work on platforms, pipelines and security in the Kurdistan Region, Iraq, and I keep going down a layer until the problem has a name. Then I write down what I found, so nobody has to dig there twice.

Role
Systems Engineer · Solutions Architect · DevSecOps
Based in
Kurdistan Region, Iraq
Now
DevSecOps Engineer, Kurdistan Region Government · DIT

Perspective

The boundaries are the interesting part.

  • Application Platform
  • Developer experience Security
  • Design Operation

The problems I like cross a boundary nobody owns. A deploy that fails because of DNS. A security control that is really a developer experience problem. A platform decision that removes a hundred future decisions, or quietly adds them.

I started in software engineering, then automated processes across finance, procurement, cybersecurity and operations at Asiacell, and moved into platform work at the Kurdistan Region Government’s DIT. The thread through all three: a platform is an operating model written down as tools, defaults and policies.

That is also why I write so much down. A fix in my head helps once. A fix written as a chart, a workflow or a rule helps every team after me.

Working method

Understanding is something you build.

When I don’t understand a system, I don’t stop at the docs. I build a small version, break it on purpose, and work down through the layers until the failure makes sense.

  1. Research. Primary sources first: the spec, the release notes, the source code. Write down what I don’t know yet.
  2. Build. The smallest version that works. Every option has to earn its place, or it goes.
  3. Break. Write the check that fails first. Then follow the packet, the trust chain or the reconcile loop until it passes.
  4. Standardize. Keep what survived: a chart, a workflow, or a rule with a code. If I fixed it twice, it becomes a check.

That is how PKI, Linux networking, Kubernetes internals, GitOps and supply-chain security stopped being theory for me. Inside the notebook

Rules I keep

Opinionated on purpose.

I keep my engineering standards in one repository: 34 skills, every rule with a code like K8S-006. These eight sit above all of them.

  1. Simple first

    Build the smallest thing that works. If I can’t say why an option exists, it goes.

  2. Intuitive defaults

    Defaults work without extra switches, and the obvious name is the right one.

  3. Secure by default

    Turning safety off takes an explicit setting. Turning it on never does.

  4. Native over wrapped

    Pass native objects and plain CLIs through. No wrapper settings, no unmaintained wrapper actions.

  5. One way

    Do the same thing the same way everywhere, so nobody has to remember which project does what.

  6. Fix the cause

    When something behaves surprisingly, fix it. Don’t document the surprise.

  7. Verify

    Run it, render it, test it. Report what ran and what didn’t. Never claim untested behaviour works.

  8. Portable

    Open protocols, such as OCI, S3, Postgres, OIDC and OTLP, so nothing is locked in without a reason.

Habits

How the work actually happens.

Agents do the typing

I work with coding agents. They load my standards before they touch a project, a hook formats and lints every file they write, and they cite the rule code when they break one. I still review, commit, push and deploy myself.

Built from Iraq

Some vendors geo-block the Kurdistan Region, so before I recommend a tool I check it works from here. It made me prefer open protocols and software I can run myself: OpenTofu over Terraform, OpenBao over Vault, any OCI registry over one vendor’s.

Written down, or it didn’t happen

If I correct the same mistake twice, it becomes a rule or a check. A hard bug becomes a field note. The common path should be safe and boring; the exceptional path should still be understandable.

My platform approach

Foundations & focus

Always a student of the system.

  • Platform engineering
  • Software supply-chain security
  • GitOps & delivery systems
  • Standards for coding agents
  • Distributed systems
  • Infrastructure security