Claude Code Handbook

English

中文

English

中文

Appearance

Who to Follow ​

Written 2026-10-04. Every link below was fetched and resolved on that date.

Claude Code changes weekly, and most of what you need to know first appears in a handful of primary sources. This page lists them, then the people whose writing helps you judge what to do with the changes. It is a reading list, not a ranking. Some posts (The Pragmatic Engineer, Latent Space) are partly or fully subscriber-only. Inclusion means the person or source published something on coding agents that was worth a Claude Code user's time recently. I left out anyone whose recent writing I could not tie to coding agents.

1. Official sources ​

2. Claude Code team and Anthropic people ​

Anthropic staff mostly speak through the official channels above. These are the individual voices with a verifiable written or recorded trail.

  • Boris Cherny, who created Claude Code. He has no blog of his own that I could confirm. Read the Platformer interview (26 May 2026) on how the engineer's job is changing, and John Gruber's note on his YC talk (August 2026), which describes having Claude Code rewrite the Claude app and verify the result itself.
  • Cat Wu, head of product for Claude Code. Her post Product management on the AI exponential (March 2026) explains how to plan roadmaps when model capability keeps moving.
  • Erik Schluntz and Barry Zhang co-wrote Building effective agents (December 2024). Anthropic has added a note that much of its tooling description has changed since, so read it for the patterns, not the tool list.

3. Independent practitioners and writers ​

4. Tool and harness builders ​

People who build the tools around or beside Claude Code often explain the design trade-offs best.

5. Researchers and educators ​

Keep up without drowning ​

You do not need all of this. Pick three to five:

  1. What's new for Claude Code changes, read weekly. Skim the changelog only when something breaks.
  2. The Anthropic engineering blog, for the few posts a year that explain why the harness works as it does.
  3. One daily or weekly generalist, such as Simon Willison or Latent Space, to see what else changed.
  4. One voice that disagrees with your habits, for example Addy Osmani on keeping judgment, or Steve Yegge on running many agents.
  5. One source close to your own stack, such as Hamel Husain if you write evals.

Read the primary source before the thread about it. A release note, a changelog entry or the author's own post tells you what changed. Commentary tells you what someone thinks about it, and arrives later and louder. When a post claims a new feature or flag, check it against the docs or claude --help before you change your setup.

Sources ​

All fetched 2026-10-04.

Released under CC BY-SA 4.0.

Copyright 2026-present Claude Code Handbook