@yibie: Every programmer should hand-write an agent. It only takes about 50 lines of code, it's fun, and it will surprise you. But to get the most out of it, do these two things: First, write it from scratch. Open a blank text file and type every line yourself. Don't use any AI, not even autocomplete. Second, rely only on the standard library documentation…

X AI KOLs Timeline News

Summary

This article encourages programmers to manually write a simple AI agent (around 50 lines of code) to deepen their understanding of how agents work, and suggests writing it from scratch while relying only on standard library and API documentation.

Every programmer should hand-write an agent. It only takes about 50 lines of code, it's fun, and it will surprise you. But to get the most out of it, do these two things: First, write it from scratch. Open a blank text file and type every line yourself. Don't use any AI, not even autocomplete. Second, rely only on the standard library documentation and API documentation (e.g., Anthropic API). You could ask Claude to help you write it, but the value of building it yourself lies in: it gives you a strong mental model of how the agent works—not a rough "LLM in a loop with tool calls," but every detail. By doing everything yourself, you won't accidentally skip important parts you haven't understood yet, and you'll directly see how quickly new behaviors emerge. My first agent had only one tool: "addition of two numbers," but it could already implement multiplication through repeated calls. Once it's running, there are dozens of things to try: add a bash tool (remember to do it in a sandbox), swap models (can the worst model still produce good results?), or build a simple memory system. — Nick Bergson-Shilcock, Recurse Center Original: https://x.com/nicholasbs/status/2070529196351238252… #AI #Agent
Original Article
View Cached Full Text

Cached at: 06/27/26, 03:57 PM

Every programmer should write their own agent.

It only takes 50 lines of code, is a lot of fun, and will surprise you. But to get the most out of it, do these two things:

First, write it from scratch. Open a blank text file and type out every line of code yourself. Don’t use any AI, not even autocomplete.

Second, rely only on standard library docs and API docs (e.g., Anthropic API).

You could have Claude help you write it, but the value of building it yourself is this: it builds a strong mental model of how an agent works — not a rough “LLM in a loop with tool calls,” but every detail.

When you do everything by hand, you won’t accidentally skip important parts you don’t yet understand, and you’ll see firsthand how quickly new behaviors emerge.

My first agent had only one tool — “add two numbers” — but by repeatedly calling it, it could already do multiplication.

Once it works, there are dozens of ways to play: add a bash tool (remember to do it in a sandbox), switch models (can the worst model still produce good results?), or build a simple memory system.

— Nick Bergson-Shilcock, Recurse Center

Original: https://x.com/nicholasbs/status/2070529196351238252…

#AI #Agent

Nick Bergson-Shilcock (@nicholasbs): Every programmer should write their own agent.

It’s fun, only takes 50 lines of code, and will surprise you. But to get the most from the experience, do these two things.

First, hand-code it from scratch. Start with a blank text file and type out every line of code yourself;

Similar Articles

@lidangzzz: I've said it many times over the years: to make an AI Agent write good code, all the secrets are in the textbooks from the 1990s: - Write tests diligently, write more tests, push test coverage as high as possible - Do CI/CD properly, avoid messing up at all costs - For a new proj…

X AI KOLs Timeline

The author emphasizes that the key to making AI agents write good code lies in following classic software engineering practices from 1990s textbooks: writing tests, doing CI/CD properly, top-down design, and modular decoupling.

@FakeMaidenMaker: The scariest thing about using an AI agent to write code is losing control: the agent runs wild, quality is inconsistent, you don’t know what stage it’s in, and it messes things up halfway through. AWS just open-sourced a set of development lifecycle workflow rules specifically designed for AI coding agents — AI-DLC — that make the agent…

X AI KOLs Timeline

AWS has open-sourced AI-DLC (AI-Driven Development Life Cycle), a set of development lifecycle workflow rules designed for AI coding agents to help developers control agent behavior and ensure quality. It supports multiple platforms including Claude Code, Cursor, and GitHub Copilot.

@Saccc_c: A few tips for beginners to quickly get started with AI: 1. Stop using conversational AI like ChatGPT and start using Agent tools that can autonomously execute tasks, such as Claude Code, Codex, Manus. 2. Write your own Skill, for example, structuring your work habits, preferences, …

X AI KOLs Following

Tips for AI beginners: Use Agent tools that can autonomously execute tasks (e.g., Claude Code, Codex, Manus), write a structured personal Skill description, and continuously accumulate context to refine effective prompts.

@Xudong07452910: This paper is a must-read for heavy users of Claude Code, Codex, or other AI Agents. It doesn't study how Agents fail on benchmarks, but a more real problem: In real development, what exactly are AI coding agents doing...

X AI KOLs Timeline

This paper analyzes 20,574 real-world coding-agent sessions to identify how AI agents misalign with developer intent, finding that constraint violations and inaccurate self-reporting are the most common failure modes, imposing trust and effort costs rather than irreversible damage.

@dongxi_nlp: I saw discussions about whether to use Python for building Agents. Go check out Shunyu Yao's ReAct source code – just a few notebooks. I remember running those simple lines of code and collapsing into my chair; it was one of the rare experiences in life. No exaggeration, these note…

X AI KOLs Timeline

A tweet discussing whether to use Python for writing AI Agents, citing Shunyu Yao's ReAct source code (just a few Jupyter notebooks), claiming these notebooks kicked off the Agent era, and criticizing the attitude of looking down on specific programming languages.