Ask HN: Best books written on “How to think”?
I feel like talking about how to think is going to be a bigger topic of discussion going forward now that we have AI, and dependence on software is really going to the next level — so since I've always gotten such amazing recommendations on HN, I had to ask this here
I have read many these kind of books, and I have found none of them to be helpful. They are just mangling delicious-sounding sentences.
I have found that the most effective way to think is to write your own book, your own expedition of the matter at hand. When you write a sentence/paragraph, you notice how poor/ugly/erroneous your writing is, and then you rewrite it. I love being noticing how wrong I am, because at that point I have learned something. This way, you have iterated and learned the matter, and learnings are not just in your brain with you all the time, but you also have externalized it in writing, and the passing of time shows if it is timeless bulletproof understanding/thinking/learning/whatever.
Would you mind listing the ones you didn't find useful? I believe 90% of everything is crap, but I want to get to the good stuff faster.
Well, maybe the best example is this: https://fs.blog/tgmm/
I have physical copies of these books. They are really well quality material, well layouted, and the content is similar to what is found at fs.blog website. All the "mental models" for thinking they include are kind of p*rn for this kind of stuff, but it is nearly impossible to apply these mental models consciously in real life, especially ad-hoc real life situation. There is no time to think each different mental model for every situation/task/problem/matter. The most effective thinking is the real-life "quick math/no BS" style of thinking, and the real superpower is if you have made your own expedition to the matter, because then you can just recall the stuff you need from your own brain quicker and better than any LLM.
Thinking is writing and writing is thinking, and thus also we've been pretty intense about the topic for a long time:
https://hn.algolia.com/?q=how+to+write
Just two cents.
Thanks. This is brilliant and makes so much sense, but it's not something I would have searched for.
This also plays along very well with OP's question. I personally always thought that AI makes me think a lot more but maybe that's because I give it massive essays while other people use it to avoid writing essays.
Not directly answering your question; but this is the advice I wish someone had told me 30 years ago.
1. Logical arguments. No one wants to be interrogated by a courtroom lawyer. Sometimes it is necessary for very high-stakes scenarios where everything must be exactly right. But nobody likes it. This is the same reason why "waterfall" gets a bad name. If the specifications were correct, waterfall won't get such a bad reputation. The reason why specifications are never correct is that nobody actually sits through and takes the time to logically define in excruciating detail what they want. The only part of logical argumentation I have found useful is agreeing upon common terminology; in any non-trivial document, you should always have a terminology section where you specify this is what you mean by X. I have witnessed massive pushback against the common definitions like what a database is or what a system owner is.
2. People problems. I would argue 20% of tech problems are people problems which are really communication problems. e.g. business people don't know how things work and what is involved in performing Y. In their minds, what they are asking for is very simple. What they don't realize is they are asking you to integrate three different pieces of software created by different vendors that are completely incompatible with each other. When the developer tries to explain the technical complexity, they think you are lying.
3. Political problems. I would argue 80% of tech problems I have encountered at work is pure power politics. This is war in the non-violent sense. People have lied to me repeatedly and actively tried to sabotage my reputation and my projects. Not to mention to accuse me of wrongdoing for things they were actually responsible for. In this land of where everything is a lie, people go with their "gut". This is where psychology is useful. It turns out their "gut" is nothing more than past biases and cognitive short-cuts. The ability to read the room is the most critical ability here.
from previous thread, a lot of good suggestions.
A succinct book which is a good primer for thinking through things is "Rulebook for Arguments" by Anthony Weston. Quick to get through and understandable.
I really like The Philosopher's Toolkit: A Compendium of Philosophical Concepts and Methods by Baggini & Fosl.
Learning to Learn the coursera course is always recommended
Philosophical Investigations
LLM’s are mechanisms simulating playing language games.