Struct Dev

new project is live 🚀 pdsexpress.online

The reason agents are so good at Linux is that all 40 million lines of kernel code was part of the pre training. Along with every other open source dependency. This really does make every obscure error message shallow, and the system completely malleable.

my eyes are blessed

Software engineering at the tipping point youtu.be/2n41YjR5QfU?si… via @YouTube

Push-based systems come up in 90% of system design interviews. Here's the exercise you should be able to solve: Design a notification system for 100M users. Some have 50 followers. Some have 10M. The instinct is to hold a WebSocket connection open to every active user and push updates as they arrive. Clean mental model. It collapses the moment a celebrity posts. When someone with 10M followers posts, you push to 10M open connections simultaneously. Your message broker saturates. Your WebSocket servers fall over. The system fails at the exact moment it needs to work. That's the fan-out problem. And it kills more interview answers than any other mistake. The production answer: push and pull aren't binary. You pick based on follower count. Users with fewer than 1,000 followers get push fan-out. Each follower gets notified immediately. Users with millions of followers get pull fan-out. Their feed assembles on read. Nobody gets a push. Followers see the post when they open the app. Twitter built exactly this: push-on-write for small accounts, pull-on-read for large ones. But fan-out is only half the problem. Push means stateful connections. Your servers now need to know which connection lives on which machine. You can't route blindly. Most teams reach for Redis pub/sub here; the WebSocket server subscribes, the backend publishes, the message finds the right node. Add a 3-second network drop and you have another layer: what did the client miss? Now you need sequence IDs, a message buffer, and reconnect logic that replays missed events. "Push-based" became push with a pull fallback, a message broker, sticky routing, and a replay buffer. Most engineers stop at the first diagram. The ones who get the offer keep pulling the thread until the system breaks.

the model alone is no longer the product

First in my bloodline to see 1 million line change PR getting merged (Bun's master branch is now rust, it's official)

‼️🚨 BREAKING: A new npm supply-chain attack uses a dead-man's switch. The payload plants a watcher on your machine that nukes your home directory the second you revoke the GitHub token it stole from you. The compromise happened today, across 42 official tanstack npm packages, 84 malicious versions in total. tanstack/react-router alone pulls more than 12 million weekly downloads. The attacker forked TanStack's repository and pushed a single hidden commit. From there, they tricked TanStack's own release system into signing the malicious packages as if they were the real thing. To npm, and to anyone checking the cryptographic proof of origin (SLSA provenance), the poisoned versions looked 100% legitimate. Maintainer Tanner Linsley confirmed the whole team had 2FA enabled. It didn't matter. This is the first documented npm worm in history that ships with a valid, signed certificate of authenticity, the same one defenders rely on to know a package wasn't tampered with.

📁 Fei-Fei Li, former Google Chief Scientist, says the industry is dangerously fixated on language models. Most of the real economy is physical, perceptual and spatial. Once AI fully understands the visual world, it stops being a chatbot and starts becoming infrastructure.

Stop adding content to your UI

The Cloudflare $5/mo plan is honestly absurd Workers - 10M requests D1 - 25B reads, 50M writes KV - 10M reads, 1M writes R2 - 10 GB storage, zero egress Email - $0.35 for 1000 emails Browser - 10 hours per month You also get Durable Objects, Queues, Workflows - included, Unlimited Hyperdrive queries, Vectors.

life really does gets better when you get back into your nerdy interests

🎬 New video: Explore Zed's source code to learn how to support multiple AI providers 💪

"Technical writing completely changed my life." - @trq212 In less than 2 years, Thariq (@AnthropicAI) cracked the code on writing technical articles that consistently pass 1M+ views. In this 15-min workshop, he breaks down:  → his exact writing workflow  → tactics behind articles that go viral  → how he leverages AI to write faster (without losing his voice)  → why technical writing is the most underrated way to drive mindshare Technical writing is one of the most powerful (and completely free) ways to gain views, build authority, and teach the world what you know. This is the 4th [Technical] Write & Learn, a curated workshop series cohosted with @swyx and @KernelLabs_ai.

React Doctor v2 is here Your agent writes bad React code, this catches it Works with Next.js, Vite, React Native. Fix your app in minutes npx react-doctor@latest

@guyokai @birdabo Opus 4.7 maladaptive

@birdabo Well, we're fucked.

everybody calm down. i got this.

my left airpod waiting for the right airpod to charge

-----BEGIN RSA PRIVATE KEY-----

new project is live 🚀 pdsexpress.online

💯 across the board