sharriy@devops:~$ cat about.txt

sharriy_

DevOps engineer. I make software ship faster and infrastructure break less.

I spend my days writing Terraform, tuning Kubernetes clusters, automating CI/CD pipelines, and figuring out why the pod is CrashLoopBackOff at midnight.

I believe the best DevOps engineers learn by breaking things intentionally — in a lab, in staging, in prod if you're brave enough. Logs don't lie. Docs become outdated. Experience compounds.

// currently: building things, writing about them, shipping them.

github ↗ ./blog

$ kubectl describe sharriy

Name: sharriy

Role: DevOps Engineer

Focus: Cloud · Containers · Automation

Cloud: AWS · Azure · GCP

OS: Linux (always)

Editor: nvim (no shame)

Status: building in public ✓

── $ which tools

Kubernetes Docker Helm ArgoCD GitHub Actions Jenkins Terraform Ansible AWS Azure GCP Linux Python Bash Go YAML

── $ git log --oneline --career

DevOps Engineer @ Building in public

2023 → present

Automating deployments, managing Kubernetes clusters, designing CI/CD pipelines, writing infrastructure as code.

Cloud & Infrastructure @ Hands-on projects

2022 → 2023

Multi-cloud architecture on AWS and Azure. IaC with Terraform and Ansible. Container orchestration from scratch.

Started the journey @ Self-taught

2021

First kubectl command. First docker build. First time breaking prod. First time fixing prod.

── $ cat philosophy.md

▸ automate everything

If you do it twice, script it. If you script it twice, pipeline it. Manual processes are technical debt that charges interest every time someone is on call.

▸ observability first

You can't fix what you can't see. Metrics, logs, traces — before you ship anything, know how you'll know when it breaks.

▸ fail fast, recover faster

Systems will fail. The goal isn't zero failures — it's fast detection, fast rollback, fast recovery. Build for resilience, not perfection.