I saw this and realised something:
"Hey, wait, where have I seen other people talk about specific benefits from Rationality?"
And then I realised I hadn't. I look around the site some. Nothing there.
This is a place to fix that. The idea of this page is to post specific things that you personally have found helpful, that you learned from your studies of Bayescraft. This way we can find some that seem to work for a large number of people, so that when new people start to become interested in Rationality we can "make it rain" so that they see the benefits that come with being less wrong.
For commenters:
If someone posted something already that also worked for you, mention that. If every tactic is apparently used by only a single person, then it is harder for us as a community to figure out what we should recommend to tyros.
List of N Things:
Understanding that my high school history class has more to do with real science than does my Chemistry class let me understand how I should be approaching the problem. History lets you look at what happened and say "Why did this happen" when you view it the right way.
Reading up on cognitive neuroscience taught me that I could use the placebo affect on myself. I have missed one day of school due to illness in my life.
Learning to not propose solutions for a minimum of five minutes, by the clock, has honestly been the most effective thing I have yet learned for personal application at Less Wrong.
May we all share many useful things, for our own benefit and as a place to point tyros towards.
Djikstra said that computer science is as much about computers as astronomy is about telescopes, so it shouldn't be surprising that things like algorithms and data structures has relevance to even mundane reality. I think one way I look at myself is an extremely small and limited computer. On the fly, my brain is slow at performing operations, I have a hard time recalling information, and I do so with limited accuracy. Sometimes I make mistakes while performing operations.
So what are we doing when we try to organize ourselves and make plans but trying to compile a program for these very far from optimal circumstances? Obviously, if I make plenty of mistakes, I need to write in plenty of redundancy; and I have to employ "tricks" in order to achieve meta-cognition at the right times (something that goes beyond the computer analogy, I know).
This involves, as I see it, a further way of looking at yourself. You see yourself as both the machine executing instructions, and the programmer writing those instructions (as well as the compiler, trying to translate the program to machine language). Nietzsche wrote that we have to develop as both commanders and obeyers. I thought this was hogwash, but I've learned that there is a lot of truth to that.