For platform engineers: provision, ship, and observe production infra with confidence.
Reach for this when you own the infrastructure behind a service and need it to ship and stay up. It takes you from provisioning cloud resources as code, through CI/CD pipelines and containerization, to running workloads on Kubernetes and seeing inside them in production. The result: a repeatable, observable platform you can hand to a team instead of a pile of one-off scripts.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Writes safe, modular, idiomatic Terraform – remote state layout, module structure, plan-review discipline, version pinning, and blast-radius control.
Designs and hardens GitHub Actions CI/CD – pipelines that hit a sub-10-minute PR feedback budget through caching and parallelism, with least-privilege security and safe deploy gates.
Produces production-minded docker-compose configurations – pinned images, healthchecks with real intervals, health-gated startup ordering, named volumes, explicit networks, and env-file secrets – plus the matching .env.example.
Writes production-ready Kubernetes manifests – Deployments with correct resource requests/limits, readiness/liveness/startup probes, PodDisruptionBudgets, safe rollouts, and graceful shutdown.
Instruments systems with the three pillars – structured logs, RED/USE metrics, and distributed traces – correlated by one trace ID, with cardinality budgets and symptom-based alerts.
Diagnose and fix a broken local development environment methodically – reproduce the failure, fingerprint runtime, package manager, OS and arch, check version files and PATH shadowing, lockfile drift, missing env vars (without printing secrets).
Runs a whole-application security audit – threat-model-lite scoping, dependencies and supply chain, secrets, authentication and authorization, input handling, transport and headers, logging, and infrastructure config.