CLOUD INFRASTRUCTURE / PLATFORM ENGINEERING / SRE

Systems change.I keep the receipts.

I build and operate cloud systems with a bias toward reliability, repeatability, security, and knowing exactly what changed when production develops opinions.

VIEW BUILDS ↘READ THE LOG →

// no unexplained drift detected. suspicious.

DRIFT MONITORLIVE

environmentprod

regionus-east-1

LAST CHANGE

CHG-0042portfolio infrastructure

PASSED

terraform-statelocked

cloudfronthealthy

s3-originprivate

drift-detected0

* production has opinions

01 / BUILDS

Things that survived contact with reality.

// this looked simpler in the architecture diagram

RESILIENT CLOUD PLATFORM

SHIPPED

Infrastructure patterns for private origins, controlled delivery, repeatable recovery, and observable change.

ML PLATFORM MODERNIZATION

BUILDING

A production-shaped ML platform with isolated environments, managed persistence, deployment automation, and operational guardrails.

EGRESS CONTROL

OPERATED

Policy-driven outbound access with infrastructure-as-code, explicit routing, auditable rules, and safer change control.

02 / EXPERIENCE

Operate it. Break it carefully. Make it boring.

NOW

CLOUD / PLATFORM ENGINEERING

Designing and operating AWS infrastructure, reliability controls, networking, automation, and platform services.

FOCUS

SRE + RESILIENCE

Recovery engineering, infrastructure-as-code, observability, incident response, and reducing operational complexity.

// rollback plan: yes

03 / ABOUT

Infrastructure should be explainable.

The Drift Log is where I document systems, platform decisions, reliability work, architecture tradeoffs, and the occasional “quick change” that became a much longer story.

The goal is simple: build systems that are easier to operate, easier to recover, and easier for the next engineer to understand.