THE COLLECTION

Library

Everything you’ve found. Nothing you need to save twice.

11 articles
Browse at your own pace.

The era of personal software

The author describes building a custom health tracking web app to collect data from his devices. He uses automated exports, a hosted Postgres database, and AI agents to log meals and give insights. He argues that LLMs make personal software cheap to build, but not a full replacement for existing tools yet.

PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet

Wiz Research found memory-safety bugs in core PHP that let attackers run code or read worker memory without login. The bugs affect PHP versions back to 5.4, and for a decade exploit building was too complex for attackers. Frontier AI models made building exploit chains practical, and PHP released a patch on October 21, 2026.

How to effectively debug when you no longer understand the code

The author fixed three production bugs with the Claude agent while not fully understanding the code. The method uses a control case, high-fidelity signals, and a matrix that maps hypotheses to facts. Teams must build data collection and verification into infrastructure. Agents give wrong answers when they only read code.

Quake Shareware, a CD-ROM just a little too full

A retrospective on id Software's 1996 Quake shareware CD-ROM, which bundled encrypted full versions of id games that buyers could unlock via a phone order system built by TestDrive Corp. The scheme relied on security by obscurity: the on-disc unlock program generated serial codes locally, so GNOMON cracked it in 39 days, aided by plaintext files and bugs. The experiment failed commercially, leaving id with ~150,000 unsold CDs.

Concurrent Servers: Part 8 - Go

This part of a series on concurrent servers shows how Go handles the problem: launch one cheap, M:N-scheduled goroutine per client, avoiding async/await since the runtime already uses epoll for I/O. It then covers cases where you should still bound concurrency—compute-heavy tasks, limited downstream resources, and malicious clients—via a channel-as-semaphore pattern or a worker pool. Tradeoff noted: goroutines are cheap, but unbounded concurrency can still exhaust CPUs or file descriptors.

How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache

Cloudflare details five Rust memory-layout changes to its 1.1.1.1 DNS cache — dropping Vec/String capacity fields, merging record lists with u16 offsets, omitting owner names when they match the query key, boxing large enum variants, and storing record data as wire-format bytes — cutting per-entry memory 56% and freeing roughly 100 TB fleet-wide. Performance also improved (inserts +43%, lookups −19%), though each change carries tradeoffs: allocator overhead and poor locality from boxing, sequential-only access for wire-format buffers, and records no longer self-contained.

Uber’s Real-Time Push Platform

Uber replaced mobile app polling—which reached 80% of gateway traffic—with RAMEN, a server-push platform built on Server-Sent Events plus a custom sequence-number/acknowledgment protocol for at-least-once delivery. Scaling forced a rewrite from Node.js with Ringpop gossip sharding to Netty with ZooKeeper/Helix, reaching 1.5M concurrent connections and 250K messages/sec. A newer gRPC bidirectional streaming version addresses delayed acks, unidirectional transport, and text-only payload limits.

How Discord Resizes 150 Million Images Every Day with Go and C++

Discord replaced a Python image-resizing proxy with a Go service after the original showed uneven workload distribution and high latency variance. Because no Go resizing package could beat pillow-simd, they built Lilliput, a Go package wrapping OpenCV and C image libraries via Cgo—accepting forked dependencies, manual memory management, and hard-to-debug leaks and race conditions. The rewrite cut server instances by 60% and reduced latency variance, but required extensive profiling, fuzzing, and custom GIF and video handling.

Debugging deadlocks in Postgres

Argues that Postgres deadlocks (SQLSTATE 40P01) usually reflect inconsistent lock ordering in transaction design, best fixed by restructuring operations into a consistent order. Case study: two seemingly identical bulk upserts deadlocked because rows were randomly ordered (a Go map converted to a slice) and Postgres acquires locks row-by-row during inserts; sorting rows solved it. Alternatives like explicit locks (FOR UPDATE, advisory locks) or jittered retries trade off parallelism and raise lock timeout risk.

Service-Oriented Architecture: Scaling the Uber Engineering Codebase As We Grow

Uber recounts migrating from a monolithic codebase to a microservices SOA (500+ services) to handle rapid growth, which solved coupling and deployment problems but introduced issues of obviousness, safety, and resilience. They adopted Apache Thrift for strict cross-language service contracts and built client-publishing tooling, drawing on Netflix Hystrix and Twitter Finagle for fault tolerance. Tradeoffs include immature Thrift tooling for Python and Node, and no header support complicating authentication and tracing.

Improving infrastructure efficiency for growing demand in the age of AI

Dropbox argues that as AI-driven demand grows, getting more from existing infrastructure matters as much as building new data centers. The post describes a system-level approach spanning power management (Deep Sleep), workload rebalancing, higher storage density via SMR drives, and failure-rate-driven hardware lifecycle decisions, reporting watts per petabyte improved over 50% since 2020. Tradeoffs include density versus power/cooling needs, energy savings versus latency, and longer hardware life versus reliability risk.