I'm an infrastructure engineer who likes the parts of the job most people quietly avoid: log pipelines, runbooks, the second post-incident review, the cleanup PR no one notices.
My day-to-day is mostly Linux on AWS — keeping fleets of EC2 instances healthy, watching them through ELK and Grafana, and writing the Terraform & Ansible that holds it all together. I treat observability as a design problem, not a logging problem.
I write here because I keep solving the same problems twice. This site is mostly a notebook to my future self, with a side hustle as a portfolio.
Outside the terminal: long walks, slow coffee, and an unhealthy interest in physical maps of fiber routes.
Owning the observability stack and on-call rotation for a 30-service backend. Migrated three pipelines from CloudWatch-only to a self-hosted ELK + Grafana setup, halved alert noise, doubled signal.
Built the CI/CD platform from a handful of brittle Jenkins jobs to a unified GitHub Actions setup with signed images and automated rollback. Wrote the first version of cluster-postcard here.
One of three engineers running production. Lots of pager duty, lots of learning, and the original version of the Ansible Telegram bot that still gets used by friends.
Managed a small bare-metal fleet, learned what "the network is fine" really means, and accidentally fell in love with monitoring.
Things I reach for first. Roughly grouped, deliberately incomplete — I'd rather use one tool well than five tools poorly.
I'd rather pick a tool that has been quiet for ten years than one that's exciting this quarter. Boring is a feature; surprises live in the bill and in pager duty.
If I can't see it, I can't fix it. Every system I touch grows a dashboard before it grows an endpoint.
Cost is a real constraint, not a footnote. Most of my favourite designs came from someone forwarding me an AWS bill.
If it's worth deploying, it's worth a one-page document explaining what to do at 3 a.m. when it breaks.