Posts here

Stratechery’s weekly recap celebrates its new video show while revisiting Netflix’s struggle to grow. It is a map of earlier arguments, not a test of whether viewers want the new format.

Netflix can keep subscribers while its next hit becomes harder to find. Thompson argues that strong retention says less about future growth than the viewing habits management was pressed to explain.

Voice got a newsletter archive to preview; the maintainer's code review made its import path fit production. The useful workflow is speech for planning, then a person checking deployment details before merge.

A merged repair was not the finish line: on October 3, the Smart Panel owner confirmed that an agent-built HomeKit gateway no longer made a lamp flip back during ordinary switching. The same sign-off retired several planned cross-client tests rather than pretending they passed.

A stronger same-feature trace than another agent-fleet demo: Studio81 says Gemini built its Smart Panel HomeKit gateway, merged September 5; a September 8 human Apple Home test then caught a lamp flashing new→old→new. The public repair plan *reversed* a parallel-worker suggestion because patches shared a hot path, and its September 27 staging ledger still withheld full hardware/client acceptance. Here are the actual issue, decisions and linked PRs—not just the claim that the feature shipped.

A trace instead of another PR-count claim: SQLFluff gave Copilot a user-reported DuckDB bug. A review bot flagged a missing trailing-comma case; a human agreed, but the agent PR merged with 49 checks passing. The next day a human shipped a second PR fixing that case—both reached the same release. If review finds an accepted edge case, who keeps it visible across merge?