Cloud & infrastructure
AWS foundations, Terraform modules, Linux hardening, networks, storage, and cost-aware architecture.
Engineering approach
How I build.
How it runs.
Explore an illustrated release workflow and the engineering disciplines behind software, AI and infrastructure projects.
Release workflow
From commit to a healthy cloud service.
An illustrated release path: every transition leaves evidence, every gate can stop the rollout, and production stays observable.
-
01
Source
Code is pushed.
A small, reviewable commit starts the release. The workflow records exactly what changed and who approved it. -
02
Continuous integration
The pipeline proves it.
Tests, dependency scanning, and policy checks run in parallel. A failed gate stops the story here. -
03
Artifact
Code becomes an image.
A versioned OCI image is built once, signed, and identified by digest so every environment receives the same artifact. -
04
GitOps release
The cluster reconciles.
A declarative change reaches Kubernetes. Health checks and rollout rules replace containers without hiding failure. -
05
Operations
The cloud service reports back.
Metrics, logs, and alerts confirm the release is healthy—and create the evidence needed to recover when it is not.
Engineering disciplines
One delivery path, four disciplines.
I work across the layers where infrastructure, software, security, and operations meet.
Platform delivery
Docker, Kubernetes, Helm, GitOps, CI/CD, release controls, health checks, and operator handover.
Security & reliability
Policy gates, supply-chain evidence, observability, recovery plans, runbooks, and failure verification.
Applied AI systems
Data pipelines, model evaluation, RAG, provenance, safe automation boundaries, and MLOps workflows.