问HN：可能是个基本问题，但我该如何有效地使用人工智能？
我是一名拥有大约七年经验的程序员，但我觉得自己在这里的许多程序员面前仍显得不够出色，而且我所做的大部分工作相对简单。我主要负责WPF和WinForms应用程序的开发，这些应用程序作为工业现场基于梯形图系统的用户界面层。
由于这项工作的性质，工作强度非常大。工厂的出差次数太多，身体上非常疲惫，而相对于所投入的努力，薪水也并不高。这就是我想成为一名以产品为导向的程序员的原因。为了朝这个方向发展，我一直在尽可能积极地使用人工智能。然而，在我目前的工作中，这很困难，因为工厂的安全措施通常比较严格，AI工具无法真正连接到那里。
我一直在阅读关于提示工程、文档风格等相关主题。我还使用OpenClaw，老实说，我觉得我已经在尝试几乎所有我能接触到的东西。在工作时，我将其与Obsidian连接，记录我认为我的代理需要的知识。
尽管如此，十倍生产力的概念对我来说感觉有些夸张。我想知道人们实际上是如何提高使用AI的能力，以及他们是如何学习这些基本方法的。关于AI的炒作太多了，很难分辨什么是真实的，学习这些东西比我预期的要困难得多。
我应该如何正确地学习这些呢？
现在我特别想学习如何管理多代理系统。我迄今为止构建或尝试的每一个AI多代理框架都失败了。起初我试图以类似TDD的方式进行控制，但那些认真使用TDD的人可能知道我所说的测试有时会变得过于局限。架构有时会开始崩溃，而代理们则不断修复那些小问题，同时代价却在不断上升。
与此同时，在韩国有很多讨论，如果你不使用AI，就会落后。因此，我一直在努力学习，以免被甩在后面。老实说，自从我开始使用AI以来，编程变得更加愉快。
其中一个原因是，编程与英语思维方式紧密相关，而这在我使用韩语时总是感觉有些尴尬。甚至写代码的过程曾让我感到心理负担很重。但有了AI，我可以用韩语思考，同时仍然有效地编写代码。
你知道当你第一次从零开始写代码时那种巨大的疲惫感吗？
当我写一个接口时，我立刻开始看到实现的数量。
当我看到实现时，我开始注意到生命周期冲突。
当我看到生命周期问题时，我开始思考所有权和处置。
当我思考所有权时，我开始考虑对象池的可能性和重置合同。
当我思考依赖注入时，我开始看到组合根和测试缝隙。
当我思考合同本身时，我开始担心未来扩展的成本。
所有这些曾让我觉得编码的过程非常沉重。
但AI只是写一个草稿，而不会被这些问题困住，我真的很享受将这个草稿重新塑造为符合我自己思维的代码。
我想在这种方式上更好地使用AI。
有什么好的方法可以提高使用AI的能力？如何在不被炒作淹没的情况下，跟上有用的趋势？
查看原文
I am a programmer with about seven years of experience, but I would say I am below many of the programmers here, and most of the work I do is fairly simple. I mainly work on WPF and WinForms applications that act as UI layers for ladder diagram based systems in industrial sites.<p>Because of the nature of this work, it is very labor intensive. There are too many factory trips, it is physically exhausting, and the pay is not great relative to the amount of effort involved. That is why I want to become more of a product oriented programmer. To move in that direction, I have been trying to use AI as actively as possible. In my current job, though, that is difficult because factory security is usually closed off and AI tools cannot really be connected there.<p>I have been reading about prompt engineering, harness style documentation, and similar topics. I also use OpenClaw, and honestly I feel like I am already trying almost everything I can get my hands on. I connect it with Obsidian and write down the knowledge I think my agents need while I work.<p>Still, the idea of ten times productivity feels somewhat exaggerated to me. I want to know how people actually get better at using AI, and how they learn the underlying methods. There is so much hype around AI that it is hard to tell what is real, and learning this stuff has been more difficult than I expected.<p>How should I study this properly?<p>Right now I especially want to learn how to manage multi agent systems. Every AI only multi agent framework I have built or tried so far has failed. At first I tried to control it in a TDD like way, but people who have used TDD seriously probably know what I mean when I say that tests can become too locally focused. Sometimes the architecture starts to fall apart, and then the agents keep fixing only those small areas over and over while the token cost keeps rising.<p>At the same time, in Korea there is a huge amount of talk that if you are not using AI, you will fall behind. Because of that, I have been trying hard to learn it so I do not get left behind. And to be honest, programming has become much more enjoyable for me since I started using AI.<p>One reason is that programming feels deeply tied to English ways of thinking, and that has always felt awkward with Korean. Even the act of writing code used to feel mentally heavy for me. But with AI, I can think through things in Korean and still code effectively.<p>You know that huge fatigue you feel when you first start writing code from scratch?<p>When I write a single interface, I immediately start seeing the number of implementations.
When I see the implementations, I start seeing lifecycle conflicts.
When I see lifecycle issues, I start thinking about ownership and disposal.
When I think about ownership, I start thinking about pooling possibilities and reset contracts.
When I think about DI, I start seeing the composition root and the test seams.
When I think about the contract itself, I start worrying about future extension costs.<p>All of that used to make coding feel painfully heavy for me.<p>But AI just writes a draft without getting stuck in all of that, and I genuinely enjoy taking that draft and reshaping it around my own thinking.<p>I want to get much better at using AI this way.<p>What are the best ways to improve at it, and how do you keep up with useful trends without getting buried in the hype?