Enjoy Newsletter #82.

How the Lobsters front page works

Because the source code for Lobsters—the computing-focused link-aggregation community—is open source, the author dug into its front-page ranking algorithm. The core formula is hotness = -1 × (base + order × sign + age), where a more negative value ranks higher on the page. base is the sum of tag modifiers (each tag carries a weight between -10 and +10; for instance, culture and rant are penalized), plus a 0.25 boost if the submitter marked themselves as the article’s author. order is the base-10 logarithm of story points plus comment points, meaning the jump from 0 to 100 upvotes has a much larger impact than going from 1,000 to 1,100. Comment points count for half an upvote each, are capped so they never exceed the story’s own score, and are ignored entirely when base is negative—preventing low-quality flamebaits from rising on comment volume alone. The sign term turns out to be effectively a no-op in practice, while age is the submission timestamp divided by a 22-hour window, growing linearly and steadily overpowering the logarithmic vote score.

The author finds the algorithm solid: new stories get a fair shot at visibility and nothing camps on the front page forever. Still, Lobsters’ distinct character comes primarily from opinionated moderation, a narrow focus on computing, and its invite-tree membership model rather than the ranking formula itself. Even when disagreeing with the most vocal commenters, the author notes that disengaging only hands them more influence, since just a few early upvotes from active users are enough to propel a story onto the front page.

Software engineers can no longer neglect their soft skills

Quan argues that starting in 2026, communication has become the single most important skill for a software engineer—surpassing raw coding speed, system design, or deep mastery of a language like Rust. The reason is the rapid leap in AI coding agents: he uses Claude Code for nearly every non-trivial task and spent over $500 on usage in December alone. With Claude Opus 4.5, vanilla Claude Code out of the box handles roughly 80% of implementation work, meaning prompt tricks and custom MCP setups are no longer real differentiators. The bottleneck has shifted from implementation to specification: the clearer the spec, the better the agent satisfies both technical and business requirements—yet arriving at a clear spec is deceptively hard.

In reality, tickets rarely capture the full requirements. Engineers have to ask probing questions to surface unstated assumptions stakeholders didn’t even realize they were making, facilitate trade-off discussions, push back on scope creep without damaging relationships, and exercise judgment on edge cases nobody thought to specify. Previously, an engineer with mediocre communication skills could still thrive on the strength of exceptional coding output; today, the non-coding parts of the job are mandatory. Engineers are conditioned to believe every problem has a deterministic solution and a “best practice,” whereas working with humans is messy and ambiguous. And you can’t outsource human communication to AI, because real communication requires empathy—something everyone needs more of right now.

Dithering - Part 2

Part two of this interactive visual series on dithering—the technique of creating the illusion of more colors than a palette actually has—focuses on ordered dithering, which uses a spatial threshold map to decide each pixel’s final color when converting grayscale images to 1-bit black and white. The author starts with basic quantization: using a single threshold collapses every shade of gray into solid black or white, whereas applying multiple thresholds across neighboring pixels turns a uniform gray region into a mix of black and white dots that preserves perceived brightness. When tiling a small threshold map across an entire image, arranging thresholds sequentially produces distracting vertical stripes because the output mirrors the map’s internal layout. A 2×2 Bayer matrix fixes this by arranging thresholds in a crosshatch pattern that distributes dots evenly; with only 4 threshold levels, however, tonal transitions still show harsh banding, which a 16-level 4×4 Bayer matrix smooths out considerably.

How the threshold map is arranged defines the visual texture of the dithered image. An 8×8 Bayer matrix (64 levels) yields finer gradients with diminishing returns; a Cluster Dot matrix groups pixels into circular halftone-like dots reminiscent of vintage newsprint; and Void and Cluster—the author’s personal favorite—uses a blue-noise threshold map to produce an organic, non-repetitive texture that blends smoothly into gray. The next installment will cover error diffusion, a family of dithering algorithms that doesn’t use a threshold map at all.

What came first: the CNAME or the A record?

On January 8, 2026, a memory-optimization update to Cloudflare’s 1.1.1.1 public DNS resolver inadvertently broke DNS resolution for a subset of users. The bug lurked in the code that merges cached CNAME chains when only part of a chain has expired: previously, the resolver allocated a new list, placed the CNAME records first, and appended the final A/AAAA records at the end; to reduce allocations and copying, the new code appended the refreshed CNAME records onto the end of the existing answer list. Many stub resolvers process answer records sequentially in a single pass, tracking the “current target name” and updating it only when they encounter a matching CNAME—so if the CNAME appears after the A record, the A record is skipped and the response is treated as empty. Linux’s glibc (getaddrinfo) hit this exact failure mode, and certain Cisco switches even entered boot loops, whereas systemd-resolved was unaffected because it searches across the entire record set.

The deeper root cause was a decades-old ambiguity in RFC 1034 from 1987: the spec merely says the answer is “possibly preface[d]” by CNAME records, without normative MUST or SHOULD keywords (which RFC 2119 didn’t standardize until 1997). While the RFCs explicitly state that record order within a single RRset is insignificant, they say nothing about the relative order between different RRsets in the same message section—or even the order of links within a CNAME chain. Cloudflare had historically placed CNAMEs first, but had no regression test enforcing that ordering. They rolled back the change, committed to preserving CNAME-first ordering permanently, and submitted an Internet-Draft to the IETF proposing to formally require CNAME records to appear in canonical chain order before final answer records.


This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026.