Augment Code(@augmentcode)
The Karpathy rules are the kind of thing you'd write at the top of a team style guide. Here is the ...
7.8Score
TL;DR · AI 摘要
文章提炼了广受关注的‘Karpathy规则’：强调编码前思考、极简主义设计、精准修改和目标驱动执行，适合作为工程团队风格指南的核心原则。
核心要点
- 编码前必须明确假设、权衡与问题边界，避免盲目实现
- 拒绝推测性功能和一次性抽象，坚持用最少代码解决当前问题
- 修改应精准隔离、风格一致，杜绝连带重构
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本（无障碍 / 无 JS 友好）
- Karpathy工程四原则
- Think before coding
- 显式假设
- 暴露权衡
- 主动澄清
- Simplicity first
- 无推测功能
- 无一次性抽象
- 最小代码量
- Surgical changes
- 范围隔离
- 风格对齐
- 零顺手重构
- Goal-driven execution
- 可验证标准
- 闭环迭代
金句 / Highlights
值得收藏与分享的关键句。
Think before coding: state assumptions, surface tradeoffs, ask if unclear
Simplicity first: no speculative features, no single-use abstractions, minimum code
Surgical changes: don't touch adjacent code, match existing style, no drive-by refactors
Goal-driven execution: define verifiable success criteria, loop until met
#软件工程#编程规范#团队协作#工程文化
打开原文Here is the summary:
- Think before coding: state assumptions, surface tradeoffs, ask if unclear
- Simplicity first: no speculative features, no single-use abstractions, minimum code
3." / X
Augment Code on X: "@karpathy @jiayuan_jy @openclaw The Karpathy rules are the kind of thing you'd write at the top of a team style guide. Here is the summary: 1. Think before coding: state assumptions, surface tradeoffs, ask if unclear 2. Simplicity first: no speculative features, no single-use abstractions, minimum code 3." / X
Don’t miss what’s happening
The Karpathy rules are the kind of thing you'd write at the top of a team style guide. Here is the summary: 1. Think before coding: state assumptions, surface tradeoffs, ask if unclear 2. Simplicity first: no speculative features, no single-use abstractions, minimum code 3. Surgical changes: don't touch adjacent code, match existing style, no drive-by refactors 4. Goal-driven execution: define verifiable success criteria, loop until met
·
1
1
9
12