THE COLLECTION

Library

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

68 articles
Browse at your own pace.

Post 50: Good Research Takes are Not Sufficient for Good Strategic Takes — Neel Nanda

The author argues that being good at AI research is only weak evidence of being good at strategic thinking about AGI. Research offers clear feedback; strategy does not, so researchers can hold bad strategic views and never correct them. He lists skills good strategic takes need and asks readers to check what evidence supports a person's strategic claims.

Post 51: Socratic Persuasion: Giving Opinionated Yet Truth-Seeking Advice — Neel Nanda

The author recommends giving advice by breaking your argument into key steps and asking the other person questions about each step. If you get an unexpected answer, you likely missed context, so you can pivot early. The method requires real humility and willingness to change your mind, and costs more time and effort than direct advice.

MATS Applications Open (Due Aug 29) — Neel Nanda

This is a recruitment call for the MATS mechanistic interpretability program run by Neel Nanda. Applicants complete a 12-20 hour research task and write-up by August 29. About 32 candidates enter a 5 week paid online phase, then about 8 enter a 12 week paid in-person phase writing a paper. The author says past scholars often publish at top ML venues.

Sparks of Weight-Space Programming: LLMs can natively read & write neural network weights

This article reports that a frontier LLM can read and write neural network weights without gradient descent. It identifies trained behaviors from raw weights, writes game-playing networks zero-shot, and edits a small share of a language model's weights to fix looping and raise math scores. Results are early; a model without looping defects could not be improved, showing limits of the method.

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.

Battling Impostor Syndrome

This essay explains impostor syndrome among software engineers: doubting your skills even with proof of success. The author suggests reframing thoughts, comparing yourself only to your past self, and writing down daily accomplishments. Techniques include mentoring both ways, asking co-workers questions, and noting what improved your mood during highs and lows.

How to make (good) pixel art effects with Claude

The author argues that AI coding agents cannot one-shot good pixel art visual effects; you must iterate. The method: have the agent write many code-driven effect drafts rendered as short videos, then pick and refine them by eye. Quality comes from repeated human judgment, not prompts. The author shares open source effects as starting references.

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.

Patch the Planet: global response coordination as agents uncover critical vulnerabilities

AI tools found two critical PHP vulnerabilities before attackers could use them. The authors propose a five-stage response framework. Maintainers confirm and fix the flaw, key groups prepare updates in private, and teams publish guidance after. The article also weighs sharing exploit details against leak risk and funds support for maintainers.

Book Review: Seeing Like A State

This review covers James Scott's book about state planning. Scott argues that governments simplify complex systems to make them easy to measure, tax, and control. These plans often fail because they ignore local practical knowledge. The reviewer likes the historical examples but questions how far the thesis applies.

The Work Required to Have an Opinion

You must work hard before you earn an opinion. You must know the other side's arguments, find facts that contradict your view, and test your ideas. The essay says most people skip this work, so most opinions stay weak.

dlab Open Source Week: Frontier AI on Your Own Hardware — Tim Dettmers

Tim Dettmers argues that AI agents make research cheap, so small university labs can compete with big labs. His lab will release an agent harness, a local inference framework, and a compaction method that halves agent costs. He tells students to change how they work, keep their identity, and attack problems that need few resources.

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.

How the Claude Code team does code review

This article describes the code review process of the Anthropic team behind Claude Code. Agents write most of the code, so machines do most of the reading and humans approve by risk tier. The tradeoff is less human review time, but mistakes still pass, so the team needs rollback, telemetry, and clear ownership.

Everyone is doing Git on S3 wrong

The article argues that Git-on-object-storage designs using a write-ahead log, like Cursor's Continuity, gain durability and read scaling but remain effectively single-writer and still need full repositories on disk. The author presents Enroute, which instead uses per-repository Raft consensus, stateless compute nodes, optimistic locking, and a segment/layer format confining deltas to commit ancestry, with S3 for durability. Reported peak exceeds 7,600 pushes per second into one repository; reads benchmark near stock Git, but clients pay more to decode served deltas, and garbage collection remains unsolved.

How to keep enjoying programming in a world of LLMs

A Haskell developer, worried about LLM-driven burnout and skill atrophy, argues against full vibe coding: you should keep writing code yourself while delegating planning, research, review cycles, and low-risk cleanup to agents. The tradeoff is accepting modest productivity gains (roughly 2x by his estimate) instead of boasting numbers, in exchange for retaining enjoyment, codebase ownership, accountability, and independence from token limits and frontier-model vendors.

When AI writes almost all code, what happens to software engineering?

Arguing that late-2025 model releases (Opus 4.5, GPT-5.2, Gemini 3) made AI-generated code good enough to supplant hand-coding, the author blends anecdotes from prominent engineers with predictions about the profession. Specialized coding skills and hand-writing code lose value, while testing, architecture, product thinking, and verification become the engineer's core role. Tradeoffs include faster shipping at the cost of quality and accountability, though the piece rests on anecdotes and largely assumes its central claim holds.

OpenCode Reloaded

This article explains how OpenCode 2 achieves instant hot reloading of plugins, config, and MCP servers. Mutating shared state from multiple plugins causes order-dependent bugs, so plugins instead register transformation functions that OpenCode replays in order from an empty state on every rebuild. The tradeoff is that plugins give up direct, arbitrary mutation in exchange for deterministic, coordinated reloading.

repr(Rust) - The Rustonomicon

This Rustonomicon chapter explains the default repr(Rust) type layout rules: alignment, size, and compiler-inserted padding. It argues that field ordering is deliberately unspecified because generic monomorphizations may need different orderings to avoid wasted space, and enums can use tricks like the null pointer optimization to eliminate tags. The tradeoff is compiler layout flexibility versus the inability to assume a stable memory layout.