DevOps-leaning developer focused on one mission: eliminating manual work.
If a process can be scripted, cron'd, or containerized, I'll do it - not because I'm diligent, but because I refuse to repeat the same task every week.
principles:
- "If it's repetitive, automate it."
- "If it can break, add retry + logging."
- "If it works, don't touch it."
- "If it doesn't work, blame the cloudflare tunnel first."Idea → Spec → Build → Test in production → Ship
No tutorial hell. I learn on things that already run, break, and need fixing.
| Category | Strong | Working on |
|---|---|---|
| DevOps | Docker, Traefik, Cloudflare, Supabase | Kubernetes, Terraform |
| Backend | Python, FastAPI, Express, Flask | Rust, Go |
| Frontend | React, Next.js, Vite | TypeScript patterns, Svelte |
- Open to: Senior DevOps roles, automation consulting, infrastructure contracts
- Not looking for: Manual data entry projects, WordPress maintenance
Solo-built automation & internal tools. Every project below shipped solo, in production, and still running.
| Project | What it does | Stack |
|---|---|---|
findar |
Web tool to find AR combinations from Excel based on payment amount + tolerance |
The hundreds-of-days streak above is kept alive by an auto-commit cronjob. Simple principle: if it can be scripted, it should be.
- Maintaining automation pipelines untuk finance & accounting workflows
- Self-hosting stack with Cloudflare Tunnel
- Infrastructure as Code - Terraform & Ansible for repeatable provisioning
- Observability - Grafana + Prometheus for monitoring production-grade bots
- Message queues - Redis & RabbitMQ for decoupling pipeline stages
Learning in production on things that already run, not in tutorial hell.
If you want to offer me a manual data-entry project - close this tab first. But if you want to talk bots, self-hosting, or flex your gacha pulls - DM away.
Off-hours: my wife is Asanagi Umi. I just do the IT support.
"I don't write code. I delete manual processes."


