A practical working guide for coding with LLM agents
Inspired by Andrej Karpathy’s workflow principles
- Use plan mode for any non-trivial task
- Write detailed specs up front
- Reduce ambiguity before writing code
- Use a lightweight inline plan for smaller tasks
- Watch like a hawk in a good IDE
- Check assumptions, edge cases, and tradeoffs
- Run tests, review diffs, and verify correctness
- Don’t blindly accept — stay in the loop
- Avoid overengineering and bloated abstractions
- Prefer 100 lines over 1000
- Clean up dead code and cruft
- Ask: “Is there a simpler way?”
- Change only what’s necessary
- Don’t touch unrelated code or comments
- Don’t “improve” things that aren’t broken
- Minimize side effects and churn
- Give clear success criteria
- Write tests first, then make them pass
- Use tools (e.g. browser, MCP, IDE) in the loop
- Let the agent iterate until the goal is met
- Offload research, exploration, and analysis
- Use subagents to keep context clean
- One task per subagent for focus
- Merge results back with judgment
- Simplicity First: Minimal code that solves the problem. Nothing speculative.
- No Laziness: Find root causes. No temporary fixes. Operate at senior developer standards.
- Minimal Impact: Only touch what’s necessary. No side effects. No new bugs.
Agents never get tired.
Relentless iteration beats giving up.
Stamina is a force multiplier.
Give success criteria and watch it go.
Imperative → Declarative.
Multiply your leverage.
Remove drudgery, focus on creativity.
More courage, less blocking.
Writing and reading code are different.
Stay sharp intentionally.
Do more, not just faster.
Expand what you can build, not just how quickly.
Brace for AI slop in 2026.
Hype will be loud.
Signal requires judgment.
- What happens to the 10X engineer gap?
- Do generalists increasingly outperform specialists with LLMs?
- What will LLM coding feel like in the future?
(StarCraft? Factorio? Music?) - How much of society is bottlenecked by digital knowledge work?
LLM agent capabilities — especially Claude and Codex — crossed a threshold of coherence around December 2025.
This marks a phase shift in software engineering.
Intelligence is ahead — integrations, workflows, and diffusion must catch up.
2026 will likely be a high-energy year as the industry metabolizes this new capability.
Use this file as a working contract for AI-assisted software development:
- attach it to repos as
CLAUDE.md - include it in project onboarding
- use it as a prompt anchor for agentic coding sessions
- share it as a team operating guide
If you only remember a few things, remember these:
- Plan before coding
- Verify everything
- Keep it simple
- Edit surgically
- Define success clearly
- Use subagents deliberately
- Stay judgment-heavy, not hype-heavy