Networking
429 Too Many Requests: Both Sides of Rate Limiting
How to handle being rate limited without making it worse, and how to implement limits that do not punish well behaved clients.
I write about why software breaks and how people figure it out. Founder of Krova Cloud, building isolated microVMs on our own hypervisor. Years of Shopify theme work and shared hosting before that. If I have not reproduced it, I do not publish it.
Networking
How to handle being rate limited without making it worse, and how to implement limits that do not punish well behaved clients.
DevOps
Not a guide to observability platforms. Just the three signals that, in retrospect, would have given me warning before nearly everything that went wrong.
AI
An honest inventory after a year of daily use: what earns its place in the loop, what I stopped opening, and where these tools are still bad.
Kubernetes
nslookup resolves and your application cannot connect. The two use different resolvers, and the difference is where the bug lives.
Networking
A missing timeout turns a slow dependency into an outage. A badly chosen one turns a blip into a retry storm. Both are common.
Performance
Everyone blames the platform. Most of a cold start is usually your own initialisation code, and you can measure exactly which part.
AI
Large diffs used to signal that somebody worked hard. Now they signal that a prompt was short. Review has to change shape.
JavaScript
TypeScript gave up. Here is why recursive conditional types hit a wall, and how to restructure so they do not.
Networking
The proxy is telling you your application failed. Here is how to read the error log line and identify which of six things went wrong.
AI
Most agent instruction files are a list of vibes. Here is what belongs in one, based on which rules measurably changed the output.
AI
Models invent plausible package names. Attackers register them. Here is why this attack works and the two checks that stop it.
Docker
Non root containers break in predictable ways. Here is how UID mapping, volume ownership, and read only filesystems produce the same error.