Aww fuck yeah. I've been trying to write a post recently about "question-centric thinking" and/or "the skill of asking 'what question should I be trying to answer now?'". It felt like it had pre-requisites of how to ask a good question.
I think this post gets at some of the implicit tacit skills I was applying.
Nice.
Reminds me of what John Wentworth says about agent foundations stuff, he's very keen on people defining type signatures (like he does in the beginning here)
I would also very much like to claim this is a good practice when asking for feedback on your drafts that you have. If it takes someone 30 min + to go through you can think for a minute at least on what you want from them and also in that way you get a lot more clear about what you're trying to express. E.g "Hey, could you check through and get back to me with a 3 sentence summary of what the core point is and whether it is embarassing to post or not" is better than "hey could you give me feedback on this?" (I think there was some post like this on LW a year or two ago).
This resonates a lot. I once wrote about what I'd say is a specific instantiation of this concept, namely that people often ask questions that appear to have a binary return type, when that is, in fact, just the wrong return type to look for. Many binary-sounding questions actually require a return type of "function that takes a potentially large number of input values and returns a boolean [or sometimes even something more complex than a boolean]". When looking for and debating binary answers to such questions, one sweeps the most interesting parts of the answer under the rug.
One way intellectual progress stalls is when you are asking the Wrong Questions. Your question is nonsensical, or cuts against the way reality works. Sometimes you can avoid this by learning more about how the world works, which implicitly answers some question you had, but if you want to make real progress you have to develop the skill of Righting a Wrong Question. This is a classic, old-school rationalist idea. The standard examples are asking about determinism, or free will, or consciousness. The standard fix is to go meta. Ask yourself, "Why do I feel like I have free will" or "Why do I think I have consciousness" which is by itself an answerable question. There is some causal path through your cognition that generates that question, and can be investigated. This works great for some ideas, and can help people untangle some self-referential knots they get themselves into, but I find it unsatisfying. Sometimes I want to know the answer to the real question I had, and going meta avoids it, or asks a meaningfully different question instead of answering it. Over time, I've stumbled across another way to right wrong questions that I find myself using more often.
In programming there is the idea of return types — constraining and declaring the type of data structure that a given method or function will return. Having a return type means I can rely on this function not to mess up something else later down the line that requires a particular input. I can more easily interpret what the function is doing (or supposed to do), and can use it more effectively in my program.
I find this a useful metaphor when thinking about how to make progress on a difficult question. It is a different angle than the "go meta" approach; it routes around the self-referential nature of asking why I think some question is answerable and reframes the question to focus more on what shape the answer must take. To ask, "What's the return type of, 'do I have free will?'" is very useful. Suppose I ask this question in a group of friends and someone laughs and tells me, "Yes! Of course you have free will." Have they answered my question? Do I still feel confused? I know I would. I don't even have to ask friends, I can just imagine friends giving me different kinds of answers, and compare this to my feeling of confusion. Would this shape of answer actually dissolve my confusion?
Often to answer confusing philosophical questions, I need a finer-grained picture of reality. I need a better causal chain of the dynamics involved in the question, a higher dimensional conception of the problem. This is useful because it lets me verify my understanding. I can follow directly the chains of cause and effect, I can see the logic clearly. A better map gives me the ability to tell if the answer is correct.
If I can't tell whether some answer is correct or not, I either haven't defined the question well enough, or my map of reality is sorely inadequate. If I can't reframe a question to have a return type it reveals my confusion is deeper than I suspected and I need to take a step back. I need to step down and focus my uncertainty into something more basic and foundational that I can get a handle on.
Consider: "Is the universe deterministic?" What's the return type of this question? A binary yes/no works, but it wouldn't resolve my confusion. How about, "How could I tell if the universe is deterministic?" The return type for this question is more answerable, and gets at my real confusion better. So how could I tell? With a detailed enough causal map of reality I could answer this question, so I would start there.
What about, "What is consciousness?" What's the return type of that question? How could you tell if your answer was correct? How could you tell if your answer was wrong? Imagine a friend saying, "I'm conscious because subjectively it feels like I am conscious" Are you less confused? How about, "Everything is conscious, everything has a subjective experience of being itself" Can you verify this answer? If there was a detailed theoretical bridge between phenomenology and cognitive science, pinned down with experiments, would that enable you to answer the question? Is that then the return type?
This is related to the idea of operationalizing your bets. When you make a prediction market, figuring out how to resolve the market is a big question, and the strategies market makers use to turn abstract, weird, questions into resolvable markets are techniques you can use yourself for personal intellectual progress. "How do I resolve this market?" is almost the same question as, "How do I answer this question?"
When thinking through difficult philosophy, asking yourself how you are going to verify the answer is an underrated tool. Not only does it help you answer the question, it acts as a diagnostic tool for discovering just how confused you are, and where the edge of that confusion lies. The next time you find yourself in some philosophical quandary with your friends consider asking yourself, "What's the return type?"