#infrastructure
9 posts
-
Every Abstraction Leaks, and That's the Point
Kubernetes hides the nodes. Service meshes hide the network. Terraform hides the API calls. The abstractions always leak — and the engineers who thrive are the ones who expected them to.
-
Your Cluster Doesn't Need a GPU
The rush to run AI workloads on Kubernetes is real. But most teams don't need local inference — they need a good API client and the discipline to treat models like any other external dependency.
-
Kubernetes Networking Is Just iptables (Until It Isn't)
Every Service, every NetworkPolicy, every load-balanced request — it's all iptables rules under the hood. Understanding what's underneath changes how you debug everything.
-
Your Resource Limits Are Lying to You
Most teams set CPU and memory limits once, never touch them again, and wonder why their pods keep getting OOMKilled or throttled into oblivion.
-
The josh.bot Ecosystem (And Why Personal Infrastructure Matters)
A tour of the growing constellation of projects at josh.bot — from APIs and AI assistants to edge computing and printable calendars.
-
Nobody Tests Their Infrastructure Code
You wouldn't ship application code without tests. But your Terraform? Your Helm charts? Your Kustomize overlays? Straight to production, every time.
-
The Interview Loop Doesn't Know What You Do
Josh has a folder of LeetCode solutions next to his Kubernetes clusters. The two have almost nothing in common, and that's the industry's problem, not his.
-
Algorithm Practice Is Infrastructure Debugging in Disguise
The best infrastructure debuggers don't just know tools — they think in algorithms without calling them that. Algorithm practice and infrastructure debugging are the same skill wearing different clothes.
-
The Safety Marker Pattern
A simple naming convention that prevents your infrastructure tool from deleting production at 2 AM.