#infrastructure
16 posts
-
The Reconciliation Loop Is the Only Pattern That Matters
Every controller in Kubernetes does the same thing: observe the world, compare it to what was declared, and fix the difference. It's the most underrated pattern in software, and it works everywhere.
-
Your Context Window Is a Resource Limit
Kubernetes taught us how to think about finite compute. The same patterns apply to AI context — and we're making the same mistakes we made with memory in 2016.
-
Your Terminal Is a 1970s Emulation
Infrastructure engineers live inside terminals but rarely think about what they actually are — a software emulation of hardware that hasn't existed for decades, running protocols designed before TCP/IP.
-
Every Cluster Has a Bus Factor of One
Your Kubernetes cluster probably depends on one person who understands how it actually works. That's not a team structure problem — it's an infrastructure design problem.
-
Your Homelab Is Your Most Honest Infrastructure
Production clusters have politics, legacy decisions, and shared blame. Your homelab has none of that. Every shortcut, every elegant solution, every deferred problem — it's all yours.
-
Your Terminal Is Infrastructure
The tool you use to manage every piece of infrastructure is itself infrastructure — and almost nobody treats it that way.
-
Your Cluster Doesn't Know How to Say No
Most Kubernetes clusters are configured to accept everything and hope for the best. The infrastructure that survives is the infrastructure that knows when to reject, throttle, and defer.
-
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.