- GitHub Actions pipelines for this Gatsby site + side projects (lint, type-check, deploy to Netlify/GitHub Pages).
- Docker Compose labs (Docker Multilang) to keep Node, Python, and Zig tooling aligned on my laptop.
- AWS internship exposure to ticket triage + CloudWatch dashboards—not production change ownership.
- Every script was scaffolded with AI prompts; I keep those logs in the repos so reviewers know the origin.
DevOps Engineer
Learning DevOps by automating my own projects
I haven't held a DevOps title yet. This page documents the guardrails I've actually built, what still breaks, and where mentorship would help.What 'DevOps' means in my world today
Evidence (student/volunteer level)
Docker Multilang
- Compose file standardizes Node, Python, and Zig tooling for onboarding.
- Manual smoke tests replace automated suites; README lists missing health checks.
- Pipeline: GitHub Actions builds images + runs linting; still figuring out caching best practices.
Portfolio deploys
- Netlify + GitHub Pages workflows validate builds before publishing this honesty site and the static template.
- Release notes + honesty logs replace formal change-management because there’s no team yet.
- Accessibility + Lighthouse checks run via CLI scripts; failures block deploys until fixed.
What I'm practicing (always with AI pair-programming)
GitHub ActionsNetlify CLIDocker / Docker ComposeAWS CLI labsBash scriptingTerraform tutorialsk6 smoke tests (local only)
Each repo documents which of these tools is “working,” “rough draft,” or “on deck” so readers know what to trust.
Where I still need guidance
- Designing CI/CD for teams bigger than me, including approvals and rollbacks.
- Monitoring stacks beyond Lighthouse + console logs (e.g., Prometheus, Grafana).
- Hardening secrets management and policy-as-code beyond
.envfiles. - Incident response drills in real production environments.
If you’re hiring for junior DevOps/platform roles and can coach through these gaps, I’d love to connect.