I assume you mean what to do in conversation and in comments on Less Wrong. The standards for things you put in print are that everything be supportable (this is never achieved throughout an entire book, but it is the goal).
This is difficult for me, because my memory is so poor that I can rarely remember the reasons for my conclusions, let alone the data behind those reasons, let alone the sources of that data. If I can remember my conclusions, I think I’m doing pretty well.
The best that I can do is be upfront about it when I can’t remember the data. This is harder to do than it sounds. It’s easy to blurt out a statement without checking whether you can support it. I did this just 2 days ago, when someone asked me about the precision and recall figures being claimed for a piece of software I had worked on. They sounded too high to me, and I said I didn’t believe them. Hours later, I realized that although I had a feeling those figures were too high, I had no memory for any specific precision and recall figures. So tomorrow I need to talk with that person again and give them a disclaimer.
My approach is to say what I think, but give disclaimers when I can’t remember supporting information. The amount of disclaiming depends on the audience. If I’m telling a child to eat his vegetables, I’m not going to give him a disclaimer saying that I can’t actually remember the nutritional content of broccoli.
I do a lot of inferential reconstruction. For instance, the Steve Jobs anecdote is from Steve Jobs: The Journey is the Reward. I say this not because I specifically remember it being in that book, but because that is the only biography of Steve Jobs that I remember reading.
I assume you mean what to do in conversation and in comments on Less Wrong. The standards for things you put in print are that everything be supportable (this is never achieved throughout an entire book, but it is the goal).
This is difficult for me, because my memory is so poor that I can rarely remember the reasons for my conclusions, let alone the data behind those reasons, let alone the sources of that data. If I can remember my conclusions, I think I’m doing pretty well.
The best that I can do is be upfront about it when I can’t remember the data. This is harder to do than it sounds. It’s easy to blurt out a statement without checking whether you can support it. I did this just 2 days ago, when someone asked me about the precision and recall figures being claimed for a piece of software I had worked on. They sounded too high to me, and I said I didn’t believe them. Hours later, I realized that although I had a feeling those figures were too high, I had no memory for any specific precision and recall figures. So tomorrow I need to talk with that person again and give them a disclaimer.
My approach is to say what I think, but give disclaimers when I can’t remember supporting information. The amount of disclaiming depends on the audience. If I’m telling a child to eat his vegetables, I’m not going to give him a disclaimer saying that I can’t actually remember the nutritional content of broccoli.
I do a lot of inferential reconstruction. For instance, the Steve Jobs anecdote is from Steve Jobs: The Journey is the Reward. I say this not because I specifically remember it being in that book, but because that is the only biography of Steve Jobs that I remember reading.