2026W38
A few interesting articles I read over the past few days
- Semantic Search Without Embeddings — The insight that reframed this for me is that embeddings nail representation and similarity but are weak at the third piece, deciding what’s actually in or out. Doug’s point that there’s no magic 0.8 threshold where something stops being a match is the crack in the whole vector-search story. His alternative, a path hierarchy tokenizer plus BM25 over a managed taxonomy, is old school in a way I found convincing, because BM25 rewards the specific category naturally since it has lower document frequency. The “long johns” versus “base layers” example is the one I’ll keep, and the real twist is that LLMs quietly make taxonomy maintenance feasible again, which is what makes the argument land now instead of five years ago.
- Choose Boring Technology — I’d absorbed the innovation tokens idea secondhand for years, but the original is sharper: you get about three, every unusual choice spends one, so save them for the actual business and not the infrastructure. What I hadn’t internalized is his framing of unknown unknowns, boring tech wins not because it’s good but because its failure modes are already documented. The Etsy story is the gut punch, a pointless middle layer that took years to remove while search latency hit two minutes and they shipped nothing. Still chewing on where the line sits, because “boring everything” is also how you end up unable to hire or move.
- EXTREME SERVER SIDE RENDERING — The trick is dumb in the best way, keep the HTTP connection open forever and stream CSS updates so the page animates with zero JavaScript. A server-side Flappy Bird running physics at 60 FPS and pushing CSS is the kind of thing that shouldn’t work, and the numbers are wild, around 500 concurrent games per core and 20 KiB/s each. Latency is the wall it can’t climb, round trips make it unplayable far from the server, which is the whole reason we moved logic to the client in the first place. My favorite detail is that it accidentally caused rolling blackouts on Fediverse servers because nothing expects a connection that never closes.
- simple is not small — The distinction I keep coming back to is Hickey’s, simple means one braid, complex means braided together, and small is a totally separate axis. The word-count example nails it, the Unix pipeline is tiny but couples aggregation to ordering, so the moment you want original file order it collapses into temp files and joins. Google Drive is enormous and still feels simple because its parts are decoupled, which inverts the instinct that fewer lines equals cleaner. The uncomfortable takeaway is that fixing complexity sometimes makes the program bigger, and that decoupling well is taste, which is the hard thing to teach.
- Doing everyone else’s job — The stat that reframed the Pareto cliché for me is his sharpening of it, 20% do 80% of the work, but the goal only gets reached thanks to the under 5% who do the thing someone else was supposed to do. The Intel patching Microsoft’s compiler story makes the point that this isn’t charity, you fix the neighbor’s problem because your own success runs through theirs. What resonated is the patch-the-dependency move being faster than navigating locked quarterly planning, I’ve done exactly that and felt vaguely guilty about it. His regret about avoiding the boring areas is the warning I’m noting for myself.
- I don’t want the details — The reframe I want to steal is swapping “why did this happen” for “what are we changing so this class of failure is less likely.” The SVP refusing the details wasn’t dismissiveness, it was trust, skip proving you’re competent and go straight to the fix. The test that gives it teeth is whether the fix survives if everyone from the incident left tomorrow, which instantly exposes “we’ll communicate better” as organizational folklore. Good explanations aren’t fixes is the line I’ll bring to the next postmortem.
- What Sun got wrong — Cantrill’s claim is almost insulting in its simplicity, Sun didn’t lose on strategy, it got bored with the mechanics of running a business. The 2005 story is the whole thesis, a startup wanted to buy Sun hardware because OpenSolaris actually worked, and Sun couldn’t be bothered to sell it, while Dell’s Steve answered a web form so well the customer felt like Steve worked for them. That’s the part that stings, the strategy was working and the company still couldn’t execute a basic sale. The kicker that Steve later became his Oxide co-founder turns the cautionary tale into something almost cosmic.
- Alice GG • Attention is all you have — The framing that stuck is that letting someone else pick what’s on your screen is handing them the key to your brain, and the Tetris effect is the proof that sustained attention literally reshapes how you think. Her catalog of the feeds is bleak and accurate, YouTube nudging you to doomscroll, Spotify’s AI slop, Reddit as LLMs talking to Russian trolls. The line about nobody putting dead kids and far-right propaganda after a pancake recipe on the old web is the one that clarified what actually changed. Her fix, going back to RSS and a slower finite internet, is the same bet I keep making with these notes, though I’m not sure it scales past people who already miss the old web.
- Forward Deployed Engineers from the trenches — javisantana.com — Santana’s contrarian hire is the part I keep turning over, he skipped the “people skills” candidates and took backend engineers because developers smell incompetence instantly and a suit loses the room. The single objective, get the customer into production as fast as possible, is a cleaner north star than any success metric, and his “customer success is a plague” line is a direct shot at optimizing for revenue extraction. Keeping technical people out of the money conversations so they don’t internalize the wrong incentive is sharp and slightly cynical. The daily-learnings documentation requirement is the boring habit underneath all of it, and probably the one that actually compounds.