Programming Digest
Programming Digest
Time in production is trickier than it looks — wall-clock, monotonic, logical, business time all behave differently. Most incidents also resolve on their own; the best first move is to pause and observe. And leaning on AI to write code you don't understand quietly kills your growth.
How users actually experience outages is very different from how operators measure them. A 1-minute average recovery can feel like an hour. Plus: the harness around an AI agent — the loop, tools, and guardrails — is where the real engineering work lives.
Depth-first search explained clearly for trees, graphs, and matrices. Plus: a fake recruiter's take-home test that hid malicious Git hooks to steal crypto wallets, and why SIMD can speed up loops by 16x with a simple five-step pattern.
Good tools disappear when they work. When you start enjoying the puzzle of fighting your tool, that's a warning sign. Also: how Netflix maps connections between thousands of services in real time, and why keeping parallelism client-side in Kafka saves you money.
Small tricks compound fast — fuzzy shell history, git pickaxe, a one-line local server. A Uniqlo x Akamai t-shirt hides a real base64 bash script that prints a colorful "Peace for All" animation. And branchless code ran 10x faster by swapping an if for a conditional increment.
CORS doesn't protect your server — it only controls what the browser lets JavaScript read. Meanwhile, random memory access patterns can be made 33% slower by breaking every hardware optimization at once. Also: a solid primer on building financial software correctly.
Autocomplete for 240M domains under 15ms using a trie and compressed disk index. Also: YAGNI isn't about saving typing time — it's about keeping options open, and AI making it "free" to build early makes that worse.
A hacked smart bulb secretly hosts banned books over WiFi — anyone nearby can browse them in a browser. Also: six SQL patterns that catch most transaction fraud without machine learning, and why RuneScape squeezed a full MMO through a 56k connection.
AI tools can generate messy code at a scale no rockstar developer ever could. Meanwhile, engineers who spot disasters in the making often stay quiet because speaking up feels risky. Both problems share a root: humans stepping back when they should lean in.
Jira's automation can run a Fibonacci generator — making it accidentally Turing-complete. Also: why dividing pixels by 255 vs 256 actually matters, and how memory layout can beat algorithmic improvements for raw speed.
AWS Lambda's networking team cut tunnel setup time from 150ms to 200 microseconds using eBPF. Stripe runs 100k test files but trims each CI run to just 5% by tracking which files tests actually open. Plus a solid intro to AI engineering covering RAG, agents, and real production challenges.
Google's IDE journey from scattered tools to one browser-based editor used by 80% of engineers by 2023 is a neat read. Also worth your time: how Pinterest spent months tracking mysterious Kubernetes crashes, only to find zombie memory cgroups from a rogue AWS agent starving network threads.
GPS uses satellite signals and Einstein's relativity fixes to pinpoint your location. Email was built for trust but runs on bolted-on fixes like SPF and DKIM. And if AI handles complex code, maybe Python's simplicity matters less than raw performance.
Bad software hides in plain sight — rigidity, fragility, immobility, viscosity. One dev built his own text editor from scratch and daily-drove it to fix real gaps. Plus, why AI agents are quietly breaking assumptions traditional databases were built on.
Shazam skips melody entirely — it maps sound to frequencies, picks the loudest peaks, and matches fingerprints across millions of songs in milliseconds. Also: an AI agent wiped a small business's entire database and backups in one API call, with two vendors sharing the blame.
Floating point rebuilt from scratch — from math to real silicon. Plus, why LLMs lack the laziness that makes good software, and a CIA-leaked git one-liner that actually saves time.
Good APIs expose little and promise less. Boring boundaries age better than clever ones. Plus: what really happens after you click "Login with Google" — tokens, redirects, and cryptographic signatures explained end to end.
Transistors power everything in GPUs. Jason built a game where you construct one from scratch. Also, five git commands that reveal codebase health before reading a single line — spotting risky files in minutes.
Too many approval layers slow teams down through waiting, not effort. AI speeds up coding but won't fix slow review pipelines. Also: shell shortcuts like CTRL+R and brace expansion that save real time, one trick at a time.
How JPEG compression exploits human vision to shrink images. Why queues don't fix traffic spikes—they just delay the pain. And how RollerCoaster Tycoon ran smoothly on 1999 hardware by turning technical limits into design features.