Kubernetes technical interviews have a problem nobody names: they ask about objects you'll never touch in production, while ignoring the mistakes that actually break real systems. Here's the map I was missing.
A healthcheck that only says "the process is responding" can hide serious business-level failures. Let's break down what the HEALTHCHECK instruction actually promises, where the standard recipe falls apart, and how to use it as the limited operational signal it really is — not as a guarantee of heal
Vivado 2026.1 looks like it's dropping Linux support for the free tier. Before you panic or dismiss it, I turned the news into a verifiable technical decision: what's actually impacted, what's worth testing, and where the real limits of this analysis are.
A HN thread with 398 points blew up the debate again: is Docker Compose in production legitimate or an antipattern? I ran my real stack on Railway for 30 days and brought actual numbers. Spoiler: it's not embarrassing if you know exactly what it costs you.
A HN post about tar on macOS made the rounds again this week. The standard answer is "use GNU tar." I went further: I reproduced the 3 scenarios that actually break production in my Railway pipeline and documented the exact fix I use.
The Canonical DDoS hit 178 points on HN and most devs read it as someone else's news. I read it as a mirror. I dug through my Railway logs, my Docker pipelines, and my Ubuntu dependencies — and what I found made me pretty uncomfortable.
Distros find out about kernel vulnerabilities at the same time as the public. I run on Railway over Ubuntu and this forced me to audit every layer of my stack. What I found isn't reassuring.
I installed Asahi Linux 7.0 on Apple Silicon and measured what actually works in my real development workflow. The GPU driver matters less than you think. What really changed is something else entirely.
I've been team Ollama since day one. Last week I tried replacing it with raw llama.cpp and a minimal wrapper. What I found forced me to rethink something I thought I'd already figured out: Ollama solves UX, not infrastructure.
32 years in the dev trenches. Here I write what I learned, what I broke, and what nobody tells you in the tutorials.
No spam. Unsubscribe anytime.