How to Get Whatever You Want

By

Read in 简体中文

如何得到你想要的一切

问题的答案

提问。

无论你想要什么,你都可以开口去要——问朋友、问陌生人、问互联网,或者问 AI。但大多数人提问的方式很糟糕,结果就是得到糟糕的回答、迟来的回复,甚至石沉大海。这篇文章讲的是如何有效地提问,得到你想要的一切——更重要的是,学会好好提问,会让你变得更好。


“提问”到底是什么意思?

励志演讲家吉姆·罗恩(Jim Rohn)说得简单直接:提问,从搞清楚”你想要什么”开始。这听起来显而易见,但大多数人都跳过了这一步。他们还没把问题对自己说清楚,就已经发出了一条含糊的消息。

这很重要,原因如下:认真把问题写下来的过程,往往会引导你找到自己的答案。当你试图精确地描述问题时,你对它的理解也在加深。你会注意到自己忽略的细节,或者发现自己逻辑中的矛盾。一个表述清晰的问题,有时候就已经解决了一半——光是这一点,就值得你认真对待提问这件事。

好好提问,你可以做到:

  • 搞清楚自己真正想要什么。
  • 让别人更容易帮到你。

黄金法则:提问者有责任说清楚

在一切之前,先接受这个原则:

说清楚问题的责任,在需要帮助的人身上,而不是在提供帮助的人身上。

遇到了问题。是最了解情况。是需要解决方案。因此,也是有责任收集相关信息、整理清楚、清晰地呈现出来——这样,帮助你的人才能真正帮上忙。

这正是 Eric Raymond 的经典文章 提问的智慧 的核心思想,这篇文章至今仍是技术社区中最广泛引用的有效沟通指南之一。


第0步:先问 AI,再问人

在联系别人之前,先问问 AI。这听起来像是走捷径,但其实这才是负责任的做法。

在开源社区和公共论坛里,没有人有义务帮你。大家都是自愿的,靠的是热心和共同的兴趣。他们的时间和精力是有限的资源。先问 AI——花的是算力,而不是某个人的下午——就像在发帖之前先查文档、搜档案一样。这是你该做的功课,得你自己做。

这也会让你变得更强。当你在向别人求助之前先和 AI 一起梳理问题,你会带着更深的理解和更好的问题去找那个人。而一个更好的问题,对双方都有好处——你能得到更有价值的回答,对方也能遇到值得认真对待的问题。一个有挑战性、经过深思熟虑的问题,可能会暴露对方文档里的漏洞、发现他们没见过的 bug,或者帮助他们完善自己的思路。这不是打扰,这是贡献。


如何求助:一个真实的例子

假设你在登录某个网站时遇到了问题。发邮件联系客服时,你会发哪封?

版本 A:

主题: 紧急!我登不进去了!

你好,我登录账号时遇到了问题,请帮我找回账号。

版本 B:

主题: 账号不存在——需要帮助找回访问权限

你好,我今天 16:30 登录账号时遇到了问题。错误提示显示”账号不存在”,但我已经使用这个网站大约一个月了。我尝试登录的邮箱是 [email protected]。谢谢。

版本 A 写起来快,但维护人员读到它时,什么都做不了。他们不知道问题发生的时间、具体的报错信息,甚至不知道你说的是哪个账号。他们不得不回邮件索要更多信息——多一轮来回,双方都浪费时间。最坏的情况是,这封邮件直接被忽略,或者用一条复制粘贴的回复打发掉,因为根本没有上下文可以处理。

版本 B 要求你提前承担责任:确认问题发生的时间、记录具体的报错信息、附上账号信息。维护人员读到后,可以直接去查日志,找到你的登录记录,定位问题。问题解决得更快,对双方都好。

还有一件值得思考的事:无论是公司客服还是开源社区,处理技术支持的人每天都面对大量模糊、懒散的问题。一个具体、经过深思、真正令人费解的问题会脱颖而出。它给了对方一个学习新东西、解决他们从未见过的问题的机会。这让问题变得有趣,让他们帮你。一个好问题是双赢的——它尊重了对方的时间,也让你的邮件不会淹没在那些普通问题里。


向 AI 提问:同样的规则,更高的要求

AI 也需要足够的上下文才能深入理解问题、给出有价值的回答。同样的原则适用——提供相关背景、描述你尝试过的方法、附上报错信息或与问题相关的具体细节。

把 AI 当作一个知识渊博的同事:自然地沟通,但要有备而来。

不过有一个关键区别:和记得你们共同历史的人类同事不同,大多数 AI 系统每次对话都是从零开始,对你是谁、你之前做过什么一无所知。这让上下文变得更加重要。不要假设它了解你的环境、你的限制或你的目标——把这些都说清楚。你给出的上下文越具体、越相关,得到的回答质量就越高。


结语:提问是你成长的方式

人们很容易把提问当作达成目的的手段——遇到问题,开口问,得到答案,完事。但好好提问不止于此。它是一种自我提升的方式。

每次你认真地写下一个问题,你都在被迫更深入地理解自己的问题。每次你在提问前先搜索一番,你都会在这个过程中学到些什么。每次你用一个精准、详细的问题换来一个精准、详细的答案,你离开时都比来时懂得更多——不只是关于这个问题本身,而是关于如何思考问题这件事本身。

得到你想要的,是眼前的目标。但学会好好提问的人,最终会想要更好的东西、更深入地理解它们,比那些只是随手发消息等回复的人成长得更快。

提问,不只是为了得到。提问,是为了成长。


更多参考:

提问的智慧

Answer to the Question:

Ask.

Whenever you want something, you can always ask for it — ask a friend, ask a stranger, ask the internet, or ask an AI. But most people ask badly, and as a result, they get bad answers, slow replies, or no reply at all. This blog is about how to ask effectively, and get whatever you want — and more importantly, how asking well makes you better.

What Does “Ask” Really Mean?

Motivational speaker Jim Rohn puts it simply: asking starts with knowing “what do you want”. That sounds obvious, but most people skip this step. They fire off a vague message before they’ve even articulated the problem clearly to themselves.

Here is why that matters: the act of carefully writing out your question often leads you to your own answer. As you try to describe the problem precisely, you start to understand it more deeply. You notice a detail you’d overlooked, or you spot a contradiction in your own logic. A question well-formed is sometimes a problem half-solved — and that realization alone is worth the effort of asking well.

By asking a question in a wise way, you will be able to:

  • Figure out what you really want.
  • Make it far easier for others to get it for you.

The Golden Rule: Responsibility Belongs to the Asker

Before anything else, accept this principle:

The burden of clarity lies with the one who needs help, not the one giving it.

It is you who encountered the problem. It is you who knows the situation best. It is you who needs the solution. Therefore, it is also you who carries the responsibility of gathering the relevant information, organizing it, and presenting it clearly — so that whoever helps you can actually do so.

This is the core idea behind Eric Raymond’s classic essay, How To Ask Questions The Smart Way, which remains one of the most referenced guides on effective communication in technical communities.

Step 0: Ask AI Before You Ask a Human

Before reaching out to a person, ask an AI. This might sound like a shortcut, but it’s actually the responsible thing to do.

In open-source communities and public forums, nobody is obligated to help you. People do it voluntarily, and their time and attention are a limited resource. Asking AI first — where the cost is compute, not someone’s afternoon — is the modern equivalent of checking the documentation or searching the archives before posting. It’s your homework, and it’s yours to do.

It also sharpens you. When you work through a problem with AI before reaching out to a human, you arrive with a deeper understanding and a better question. And a better question benefits both sides — you get a more useful answer, and the helper gets something worth engaging with. A challenging, well-researched question can expose a gap in their documentation, surface a bug they hadn’t seen, or help them refine their own thinking. That’s not a burden. That’s a contribution.

How to Ask for Help: A Real Example

Let’s say you encountered an issue logging in to your account on a website. When you contact customer support via email, which would you send?

Version A:

Subject: Emergency! I can’t log in!

Hi, I’m having trouble logging in to my account, please help me recover it.

Version B:

Subject: Account not found — need help recovering access

Hi, I encountered an issue logging in to my account today at 16:30. The error message says “Account does not exist”, but I’ve been using your website for about a month. The email I tried to log in with is [email protected]. Thanks.

Version A is quick to type, but when the maintainer reads it, they can’t do anything useful. They don’t know when it happened, what error appeared, or even which account you’re referring to. They have to reply asking for more information — an extra round of emails, wasted time on both ends. In the worst case, the email is simply ignored or dismissed with a copy-paste response, because there’s no context to work with anyway.

Version B requires you to take responsibility upfront: check when the problem happened, note the exact error message, include your account details. When the maintainer reads it, they can go directly to the logs, find your attempt, and debug it. The problem gets solved faster, for both of you.

And here is something worth thinking about: people who handle technical support — whether in a company or in an open community — face a flood of vague, lazy questions every day. A question that is specific, well-researched, and genuinely puzzling stands out. It offers the helper a chance to learn something new, to solve a problem they haven’t seen before. That makes it interesting. That makes them want to help. A great question is a win-win — it respects the helper’s time, and it gives your email a fighting chance of not being drowned in the ordinary ones.

Asking AI: Same Rules, Higher Stakes

AI also needs enough context to understand a problem deeply and give a useful answer. So the same principles apply — provide the relevant background, describe what you tried, and include any error messages or specific details that relate to the issue.

Treat AI like a knowledgeable human colleague: communicate naturally, but come prepared.

There is, however, one key difference worth knowing: unlike a human colleague who remembers your history together, most AI systems start each conversation cold, with no memory of who you are or what you’ve worked on before. This makes context even more critical. Don’t assume it knows your setup, your constraints, or your goals — spell them out.

The more specific and relevant the context you give, the higher the quality of the answer you’ll get.

Closing: Asking Is How You Grow

It is easy to think of asking as just a means to an end — you have a problem, you ask, you get an answer, done. But asking well is more than that. It is a form of self-improvement.

Every time you sit down to write a careful question, you are forced to understand your own problem more deeply. Every time you search before asking, you learn something along the way. Every time you get a sharp, detailed answer to a sharp, detailed question, you walk away knowing more than you did before — not just about the problem, but about how to think through problems in general.

Getting what you want is the immediate goal. But the person who learns how to ask well ends up wanting better things, understanding them more deeply, and growing faster than the one who just fires off quick messages and waits.

Ask not just to receive. Ask to learn.

Further reading & watching:

How To Ask Questions The Smart Way


Discover more from Antony 's Innisfree

Subscribe to get the latest posts sent to your email.

Posted In ,

Leave a Reply

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)