请问HN：你的编程环境是什么样的，费用是多少，你觉得它怎么样？
我对“氛围编码”（定义见下文）的体验并没有像其他人在Hacker News上所报告的那样好。如果你也尝试过氛围编码，我很想听听你的设置——以及它对你来说的效果。欢迎使用以下格式回复：
```
使用案例：
[你正在使用氛围编码构建或完成的内容]
使用工具：
[AI助手或平台的名称]
费用（美元）：
[金额]
费用频率：
[每天/每周/每月]
费用包括：
[订阅费/API费用/两者]
满意度：
[你交给AI的任务中，有多少百分比完成得让你满意？]
实用性：
[总体来说，你觉得氛围编码有多实用？]
```
根据Andrej Karpathy通过Simon Willison的帖子定义的内容，氛围编码是一种软件开发风格，其特点是与AI编码助手（如Cursor或Aider）进行高度对话、低投入的互动，开发者将大部分实现细节委托给模型。开发者不再手动编写代码，而是给出自然语言提示——通常是模糊或不精确的——并在几乎不进行审查或编辑的情况下接受AI的输出。
这种工作流程通常包括：
- 请求小的、迭代的更改（“减少填充”、“修复此错误”）
- 依赖AI理解意图并生成或修改代码
- 复制粘贴错误信息而不做解释，让AI来修复
- 很少阅读差异或深入代码，除非出现故障
- 优先考虑速度和探索，而非精确或深入理解
氛围编码通常用于原型、侧项目或创意实验——在这些情况下，快速结果比长期可维护性或代码清晰度更为重要。它代表了一种从手动编程到基于提示的软件塑造的转变，开发者更像是导演而非编码者。
查看原文
My experience with "vibe coding" (defined below) hasn't been as good as what others report on HN.<p>If you’ve done vibe coding, I’d love to hear about your setup — and how it’s working for you. Feel free to respond using the format below:<p><pre><code> Use case:
[What you're building or doing with vibe coding]
Tool used:
[Name(s) of AI assistant(s) or platform(s)]
Cost in \$:
[Amount]
Cost frequency:
[per day / week / month]
Cost includes:
[subscription / API costs / both]
Satisfaction:
[Of the tasks you give to the AI, what percentage are completed to your satisfaction?]
Usefulness:
[Overall, how useful do you find vibe coding?]
</code></pre>
Definition based on Andrej Karpathy via Simon Willison’s post [0].<p>Vibe coding is a style of software development characterized by a highly conversational, low-effort interaction with AI coding assistants (such Cursor or Aider), where the developer delegates most of the implementation details to the model. Instead of writing code manually, the developer gives natural language prompts — often vague or imprecise — and accepts the AI’s output with minimal review or editing.<p>The workflow typically involves:<p>- Asking for small, iterative changes (“reduce padding”, “fix this error”)<p>- Relying on the AI to understand intent and generate or modify code<p>- Copy-pasting error messages without explanation and letting the AI fix them<p>- Rarely reading diffs or digging into code unless something breaks<p>- Prioritizing speed and exploration over precision or deep understanding<p>Vibe coding is often used for prototypes, side projects, or creative experimentation — situations where quick results matter more than long-term maintainability or code clarity. It represents a shift from manual programming to prompt-based software shaping, where the developer becomes more of a director than a coder.<p>0. https://simonwillison.net/2025/Feb/6/andrej-karpathy/