2026W29

A few interesting articles I read over the past few days

July 27, 2026

This is the output of an automated process. Every Sunday, a script retrieves articles I've saved and read, uses AI to expand my quick notes into something more coherent, then publishes them. This post is one of those articles.

Appaji - Software Engineer — The detail that got me is that you didn’t even need to run anything. Just opening the take-home project in VSCode could fire the payload through a hidden .vscode config, no git command required. I’ve cloned strangers’ interview repos without a second thought, and the $10-15k/month offer for a junior role should have been the tell. When the “recruiter” was confronted, they deleted their LinkedIn account on the spot.
How ScyllaDB’s Trie-Based Index Delivers Up to 3X More Throughput — The number that landed is 1/7th of the storage bandwidth at the same request rate. What makes it work isn’t the trie itself but packing parent and child nodes onto the same 4KB page, so an entire index neighborhood loads in a single I/O even on a cold cache. It made me want to go look at how our own index reads map onto page boundaries, because that’s where the win actually comes from.
Are we offloading too much of our thinking to AI? — The distinction I’m keeping from this is between automating work and automating agency. The Portugal story, where she and her sister argued out colonial history together before asking the model, captured exactly the thing I don’t want to hand away. The identical AI-generated physics homework is that same failure at scale. I’m still figuring out where my own line sits, and she’s honest that she hasn’t found hers either.
How Pizza Tycoon simulated traffic on a 25 MHz CPU — Pizza Legacy Blog — The trick I liked most is that they baked direction into the road tiles themselves, so cars never pathfind at all. Because roads are one-way, an east car and a west car can never collide, and half the pairwise checks return before any coordinate math runs. The real takeaway is the author’s, that the 1994 game simply never attempted the hard problems he kept reinventing in his modern port. Constraints did the design work for them.
We’re building Postgres in Rust. Using the LLVM of databases — The framing that clicked is one reliable core with many SQL frontends compiled down to the same bytecode, the way LLVM decouples languages from backends. Their argument that everything reduces to B-trees and a VDBE is clean, and compiling Doom to that bytecode is a stunt that actually sells the VM as general purpose. I’m not fully sold that Postgres wire and semantics compatibility is as close to “just another frontend” as they make it sound, but the self-updating materialized views are the part I’d want first.
The Graph That Should Be Front-Page News — The 2023 line leaving the entire historical envelope is the kind of chart you can’t unsee once you’ve looked at it. What reframed it for me is that El Niño is natural, but it now swings around a much warmer baseline, so the same cycle lands harder every time. The 90% of excess heat going into the oceans also explains why the surface feels deceptively slow while the system underneath keeps loading up.
Making 768 servers look like 1 — PlanetScale — The detail that stuck is OpenAI running 50 read replicas on a single primary and still hitting a wall, because replicas buy you read capacity but never write capacity or storage. The actual engineering is the router doing query parsing, planning, and pooling so the app just sees mydb.pscale.com and stays ignorant of the 256 shards behind it. Sticky connections pinned to one router for the connection’s life is the sort of thing I’d expect to bite someone during a rolling deploy.
The Memory Heist — Scary in an elegant way. Direct URL exfiltration was blocked, so the researcher had the model walk a site’s link graph letter by letter, through alphabetically organized pages, to spell out the user’s name and employer. The fake Cloudflare check that only shows up to the agent is a nice touch. “It just kept typing” is the line I keep coming back to, and disabling external link following feels like closing one door in a house with a lot of windows.
lobste.rs is now running on SQLite — The counterintuitive result is that CPU and memory both dropped after leaving MariaDB, not just the ops overhead of running a separate service. I keep expecting the tradeoff to show up somewhere and it mostly doesn’t at this size. The part everyone skims past is the Rails bug that deleted 3.2 million comment votes mid-migration, which is the real cost of doing this on a live site. Reads nicely alongside the jvns SQLite post further down.
Prioritize mental health — Raw and hard to read as someone in the same field. His point about LLMs is the sharpest thing here: they let him skip the path that used to force him to test his own work, so the sloppiness got hidden instead of fixed. What I’ll remember is the admission that a lot of the frustration piled on top of the depression came from simply not communicating with the people around him. Wishing him the year he says he needs.
Regressive JPEGs: (Maurycy’s blog) — I had no idea each progressive JPEG scan sets its own spectral range, which means a later scan can overwrite pixels an earlier one already drew. He abuses that to pack a whole video into a single valid .jpg that animates as it downloads. The real constraint is that decoders bail after a fixed number of scans, around 90 in Chrome, so he reduces each frame to a single DC-only scan to fit more of them. Playback timing depends entirely on network delay, which makes it beautifully useless.
Learning a few things about running SQLite — The immediately useful tip is ANALYZE, which took a full-text query from 5 seconds down to 0.05 by giving the planner real statistics. But the lesson I’ll actually carry is the single-writer constraint, where one slow DELETE blocks other writers into a 5-second timeout and takes the whole app down with it. Her fix, batching deletes into small chunks to stay under that timeout, is the unglamorous kind of thing that keeps SQLite viable in practice.