Jun 8, 2026Agentic Coding
@bcherny reflects on a year of Claude Code since GA
@bcherny and @_catwu sat down to discuss how Claude Code has evolved a year after its general availability, covering workflow shifts like using auto mode over plan mode and coding from a phone.
Score breakdown
Composite
4.7
out of 10
Novelty · 25%
4
Novelty
Impact · 43%
5
Impact
Credibility · 12%
6
Credibility
Depth · 20%
4
Depth
Weights applied. How scores work ↗
Why it matters
The post offers a first-hand account of how Claude Code's workflows and usage patterns have shifted over its first year since general availability, including mobile-first coding and automated bug-fixing routines.
- 01@bcherny and @_catwu sat down to discuss Claude Code a year after its general availability
- 02Claude Code's internal demo initially received two distinct reactions on Slack
- 03@bcherny now uses auto mode instead of plan mode
Summary— our read of the original
No summary available yet.
Key facts
- 01@bcherny and @_catwu sat down to discuss Claude Code a year after its general availability
- 02Claude Code's internal demo initially received two distinct reactions on Slack
- 03@bcherny now uses auto mode instead of plan mode
- 04@bcherny uses routines to fix bugs before they are noticed
- 05@bcherny does most of his coding from his phone
- 06The conversation includes discussion of where the Claude Code product is going
Topics
Methodology
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 9, 2026 · 17:05 UTC. How this works →