LLMs reward expertise
https://www.seangoedecke.com/llms-reward-expertise/📌 【深度思考】LLM 正在讓每個人都變成通才,但真正的差異在於「領域專業」
TL;DR:LLM 降低了技術門檻,但真正的 Prompting 核心不在技巧,而在於對該領域的專業知識。
在 2010 年代,如果你不懂 CSS,你只能依賴同事或在網路上苦苦搜尋答案;但現在,透過 LLM,每個人都能寫出「還算及格」的 CSS。LLM 正在將每個人都變成通才,但也因此產生了一個誤解:認為使用 LLM 只是「下指令」的技術問題。
🤔 當「指令技巧」無法成為護城河
許多人認為只要學會「Prompt Engineering」,就能從 LLM 獲得頂尖成果(如博士級數學解法或高品質程式碼)。然而,由於大家使用的模型大同小異,單純的「指令技巧」產出的結果往往大同小異。
真正的差異在於:Prompting 最核心的技能,其實是對該領域的專業知識(Domain Expertise)。
🧩 從數學大師 Terence Tao 的對話看出的啟示
數學家 Terence Tao 與 ChatGPT 討論關於 Jacobian Conjecture 的反例對話,展現了專業人士與一般使用者截然不同的互動模式:
- 切換模式:專業人士透過簡短、精確的訊息,將模型從「向外行解釋」模式,切換到「與數學家對話」模式,使輸出更簡潔。
- 精準修正:他不會直接否定模型,而是使用「這看起來比我想像的更複雜」等方式進行引導。
- 主導節奏:他會自行進行邏輯跳躍與建議,幾乎不會被動地接受模型對下一步的建議。
- 核心關鍵:這種互動並非靠「指令技巧」能達成,而是因為他能從模型長篇大論的回答中,精準提取關鍵概念,並識別出「哪裡看起來很奇怪」。
💡 為什麼領域知識能壓榨出更多價值?
對工程師而言,擁有對程式碼庫(Codebase)的深刻理解,能讓你比一般人更有效地驅動 LLM:
- 精準導向:當你對系統設計有預判時,你可以直接指出:「不,我覺得這裡可以更簡單」、「我們不是已經有 X 了嗎?」或「能否用我們熟悉的術語來表達這個問題?」。
- 具體細節勝過通用原則:系統設計往往由具體的細節決定,而非通用的原則。擁有對現有系統的熟悉度,比擁有深厚的軟體系統通識更能發揮 LLM 的效能。
- 打破瓶頸:在許多任務中,人類才是瓶頸,因為最難的部分在於「如何精準溝通出人類想要的解法」。資訊其實已經存在於模型中,但需要聰明的人類將它「拉」出來。
⚠️ 專業知識的必要性
雖然有人認為 OpenAI 的數學 Prompt 似乎不需要專家,但實際上,OpenAI 仍需由專家團隊來核對並過濾模型所提出的發現。目前的 LLM 仍無法跳過「專家驗證」這一步驟。
🎯 實務啟示
當你在使用 AI 工具時,不要只專注於學習「如何下指令」,而應專注於「深化你的專業領域」。當你對問題本身有深刻理解時,你才能從模型中榨取超越平均水準的價值,並在 AI 變得更強大時,依然保持不可取代的價值。
🔗 來源
- 標題:LLMs reward expertise
- 作者/機構:MaxMussio
- 連結:https://www.seangoedecke.com/llms-reward-expertise/
#LLM #AI #PromptEngineering #DomainExpertise #SoftwareEngineering #MachineLearning #ArtificialIntelligence #TechTrends #DeveloperProductivity #GenerativeAI
原始資料 Hacker News · 收集於 2026-08-04
摘要原文
In the 2010s, if you had technical gaps (say, you couldn’t write CSS), you had to either rely on a skilled colleague or just hope that the answer to your exact problem was out there on the internet. Today, everyone can write sort-of-okay CSS by delegating the task to an LLM. LLMs make everybody into a generalist. Because of this, lots of people don’t think there’s any skill involved in working with LLMs. If you want the product that LLMs can deliver — PhD-level mathematics, pretty good but sometimes tasteless computer code, or awkward LinkedIn-style writing — you can simply ask for it. Since everyone is talking to the same models, “skilled prompters” are getting the same results as people touching LLMs for the first time. This is wrong. The most important skill in prompting is expertise in the domain you’re prompting for. A good illustration of this is Terence Tao’s conversation with ChatGPT about the recently-discovered counterexample to the Jacobian Conjecture. This is not the same ChatGPT I talk to! I couldn’t get to where Tao gets, even with unlimited tokens to burn. There’s a lot to learn about good prompting from Tao’s conversation. Here are a few observations: Tao’s messages are very short and to-the-point. He doesn’t respond point-by-point to the model, just to the gist The model outputs are much more concise than when I try and talk to GPT-5.6 Sol about mathematics. By signalling expertise, Tao shunts the model into “talking-to-mathematicians” mode, not “explaining-to-amateurs” mode Tao pushes back when the model’s responses look wrong, but he doesn’t directly contradict; instead, he says things like “this looks more complex than I was hoping for” Tao makes several leaps and suggestions himself. He almost never takes the model’s advice about where to go next However, you can’t prompt like Tao on mathematical questions just by following these tips. The key to his technique is actually understanding the mathematics: pulling the relevant idea out of ChatGPT’s multi-paragraph response, suggesting alternate approaches or formulations, and identifying what “looks weird”. Terence Tao is a better mathematician than I am a programmer. But the idea here — that domain knowledge makes you better at using LLMs — is something I’ve also experienced in my own work. If you have a good theory of your codebase , you can push the LLM much harder than if you have no familiarity. Because you have your own sense of what a good solution might look like, you can say “no, I think it could be simpler here”, or “but don’t we already do X?”, or “can we express this problem in these familiar terms?“. This touches on an idea I’ve written about before : that system design problems are dominated by concrete specifics, not generic principles. Of course both are useful, but I’d rather have familiarity with the codebase than a deep general understanding of software systems. In his conversation, Terence Tao asks a lot of specific questions like “does X work here?”, or “given Y and Z, why A?“. I can’t ask those questions about the Jacobian Conjecture, but I can ask them about the systems I own at GitHub. If you have no domain knowledge, you can cling onto the LLM to at least get something . That’s not bad ! But if you have domain knowledge, you can wring far more value out of the same LLM by steering it hard in the direction you want. Most of us will have to do a mix of both these approaches, since we have domain knowledge in some areas but not others. The usefulness of domain knowledge suggests that human expertise will continue to be useful even as models get stronger. For many tasks, the human is the bottleneck, not the model , because the difficult part is in communicating to the model exactly what kind of solution the human wants. The information is “in the model” already, but it takes a very smart human to pull it out. edit: this post got many comments on Hacker News. Some commenters share their anecdotes about how expertise has helped and lack of expertise has hurt. Other commenters say it’s plausible, but they have a sensible suspicion of a view that’s reassuring them about how they’re still valuable. I agree with that, though I suspect by the time we get around to studying this, the landscape will have changed under our feet again. Some commenters point out that OpenAI’s math prompts were inexpert, and so expertise isn’t required. Here I’d respond that OpenAI do have a team of expert mathematicians that checked and filtered the model’s suggested discoveries, and that you cannot currently skip that step. If you liked this post, consider subscribing to email updates about my new posts, or sharing it on Hacker News . Here's a preview of a related post that shares tags with this one. Powerful AIs might escape containment by releasing themselves as open-weight models Before large language models, people who worried about AI safety often talked about the “boxing problem”. It goes like this . Suppose some genius figures out artificial intelligence in a late-night coding session on their laptop. Because they’re a genius, they’re smart enough to disable internet access on the laptop before turning it on. In order to escape to the outside world (and begin self-replicating) it would need to convince its creator to “open the box”. Would that work? Could a sufficiently smart AI convince anybody to let it out? Continue reading... (844 points, 348 comments on Hacker News)
由 tencent/hy3:free 自動生成