Tag: Claude Code
All the articles with the tag "Claude Code".
-
The Model Has No Memory: Context Is State, and Every Turn Is a Full Re-render
You think the agent remembers you; really it re-sends the full messages array every turn. LLM calls are stateless — "conversation" is a client illusion.
-
An Agent Is Just a While Loop? From UI = f(state) to action = LLM(context)
An agent is a while loop whose function isn't pure. Series opener from UI=f(state) to action=LLM(context), with a 32-line runnable tiny-agent.
-
3 Principles Fiber Teaches Us About AI Agent State Design
How Fiber's three mechanisms (double buffering, time slicing, lanes priority) map to AI Agent state design — three principles I stole and dogfooded.
-
Ponytail Hit 73k Stars in Three Weeks: A Side Project Cured AI Agents' Over-Coding Disease
DietrichGebert's ponytail launched on 2026-06-12 and climbed to 73k stars / 3,848 forks in three weeks, covering 16 agent ecosystems. Its core is a 7-step decision ladder that forces AI to obey YAGNI. I ran an A/B test against a 196-line TableOfContents component from this blog; after installing ponytail the review recommendation was to cut it to 25-30 lines, a -84% change. Inside — firsthand test data, three structural reasons for the viral growth, a step-by-step breakdown of the ladder, and three counter-boundaries.
-
WeRead's Official Agent Skill: The First Chinese Content Platform to Ship One — But Is the Indie Dev Monetization Window Actually Open?
微信读书 (WeRead) shipped its official Agent Skill on 2026-05-17 — the first "official player" among Chinese content platforms. Community forks exploded in the first week; six weeks later there is still not a single commercialized product. This post unpacks the three structural blockers behind the "official access + community boom + zero commercialization" pattern, and what indie devs can actually cash in on right now.
-
The 90-Day Spaghetti Point: Why Maintenance Is Vibe Coding's Real Exam
When Karpathy coined Vibe Coding in Feb 2025, he only talked about how good it felt to write. GitClear's 211M-line study and the 2026 wave of rescue jobs both map that feeling onto a 4x maintenance bill in year two. This post unpacks the three mechanisms that detonate around day 90 — the Spaghetti Point — and how to keep AI speed without paying that bill.
-
The CLI's Second Spring in the AI Era: Three Structural Reasons Behind the Claude Code / Codex / Charm / Ink Surge
Starting in 2025, Claude Code, Codex CLI, Charm Bubble Tea, and Ink all took off at once. After 30 years of GUI dominance, the CLI suddenly became the default form factor for AI tooling — Claude Code itself even ships as a Bun binary. This isn't nostalgia. Three structural constraints — LLM I/O, controllable long-running tasks, and cross-tool interop — are pushing engineers back to the terminal. Includes a 30-line Claude Agent SDK sample.
-
After the Loop Is Running: A Playbook for Verification, Comprehension, and Cognitive-Surrender Debt
blog191 walked through the five components of Loop Engineering and named three debts—verification, comprehension, cognitive surrender—without offering a treatment plan. This post fills that gap: a Wharton 1,372-person experiment, Anthropic's 52-engineer study with a 17% comprehension gap, a real $4,200 overnight bill, Claude Code's PreToolUse rejection hook, and three checkpoint patterns—the full playbook in one place.