#Kubernetes
Your Cloud Bill Is A Tax On Someone Else's Resume
Kubernetes adoption is often a tax on someone else’s resume. How solo founders end up with $600 AWS bills — and the one-VPS stack that replaces it.
My Agent Runs 10 Cron Jobs. Three of Them Are Worth the Electricity.
My always-on AI agent has ten cron jobs. Six of them went silent weeks ago and I hadn’t noticed. Here’s what the logs actually said.
The $30/Year Stack for Launching Small Bets
Professional email, chat widget, uptime monitoring, analytics — the unsexy infrastructure that makes solo projects look legitimate, for the cost of a month’s lunch.
I Found a Cryptominer in My Client's Production Cluster. Claude Code Found the Attacker.
A New Year’s security incident, a CVSS 10.0 vulnerability, and an hour-long investigation that should have taken days.
I spent years on Kubernetes. Now I'm betting against it.
Solo devs don’t need complexity. They need deploys that work.
AWS Is Overrated
Indie devs don’t need the same cloud as Amazon.
Why Your SaaS Needs a Docker Compose Setup Even If You’re Just One Person
Because the only thing worse than debugging production is debugging your local machine.
The Kubernetes Controller That Auto-Reloads Your ConfigMaps
It fixes a problem so fundamental, you wonder why Kubernetes didn’t do it first.
When DIY Beats Managed Kubernetes
When I first started working with Kubernetes, I immediately gravitated toward managed offerings like EKS, GKE, and AKS. The promise was compelling: let AWS/Google/Azure handle the control plane while you focus on your applications. Fast forward a few years, and I’ve come to a somewhat contrarian position—for many teams, especially those with some ops capability, running K3s on virtual machines often makes more sense than using managed Kubernetes. Let me explain why, and the important caveats to make this approach work.