How To Know Everything
markgreville.ie
markgreville.ie
One good trick is to ask people to make their questions as short as possible.
One speaker asked to use up to 8 words per question (and he actually counted the words and rejected the long questions;)
Another speaker had a list of pre-submitted questions, and he deliberately ignored long questions, and only answered the short ones.
Just because it's short doesn't mean it's not exceptionally vague.
This approach puts the onus on the questioner to be as concise as possible, which is not too much to ask in consideration of the audience.
It becomes more difficult to grandstand when the audience recognizes that the objective is to collect a set of questions as quickly as possible and you taking 5 minutes to set your question up is at best tedious and at worst insulting to everyone in attendance.
This is also very common on Twitter. Someone states a generic observation and people nail them with exceptions.
The question was "It's often said that the U.S. won the Cold War. Do you agree or disagree, and why?"
I asked it of Michael Kinsley, Strobe Talbott, and Bernard Henri-Lévy. You'll have to watch the YouTube videos to find it. I remember Kinsley immediately got all political and said that Reagan didn't deserve the credit.
For some reason, I stopped. I don't know why. It would have been fun to ask Lady Gaga or Taylor Swift, for instance.
Eventually, the guests would have gotten wise to it and had an answer ready.
"Disagree. There was no war."
Eric Schmidt asked both John McCain and Obama, "How would you sort a million 32-bit numbers in 1K of memory?"
McCain laughed and said "I guess I should have studied for this!"
Obama had been tipped off on that question. He stroked his chin and said "Well, I don't think the bubble sort is the right choice here."
I think the correct response would be, "Why are you asking me a question to which you presumably already have an answer, or at least an opinion on? Why don't you just share your views on this with the audience?"
Umm ... when I browse Google Tech Talks, there are lots of famous people there. It still wouldn't make sense asking them this question.
"I'd call up Jon Bentley."
The best way to learn isn't to ask questions, but to make bold statements and then listen carefully when people correct you. People put in much more effort to tailor their explanations to you personally when they try to convince you that you are wrong than when they try to teach. The only drawback is that people will prove you wrong from time to time, so only people who aren't afraid of being wrong can do this properly.
That said, in a non friendly setting.. it's one of the most efficient way to get things done. Those contexts (like work) are often adversarial and full of opposite incentives, and tapping into people's deep desire to either assert their skills or express deep belief is just way too efficient.
I've tried the friendly honest way.. it was a catastrophe, nobody wants to give you friendliness, it's a currency. Proving you wrong is an intrinsic self-reward.. it comes in abundance.
I had the experience in the other direction. I was in a team of experts (me not being one of them). My work required occasionally consulting them for their expertise (i.e. I was not expected to become deeply knowledgeable in that domain). Whenever I'd ask a question, I'd either get no response, or a quick, short response that was either incomplete, didn't address at all what I was asking, or plainly wrong given the context.
I got quite frustrated and eventually had to resort to the tactic your parent talked about: When I wouldn't get a proper answer, I would send an "update" laying out the course of action I was about to take - and it was clearly the incorrect one. Suddenly I'd get a lot of useful responses explaining why what I was doing was wrong and how to do it properly.
So yes - this is a bad tactic to do in general, but there are times when it's called for. If you're in a team where you feel the need to do this, find another job. I did as soon as I completed the project.
Editing a draft is easier than creating from scratch. If you ask an expert open ended questions, you are creating a lot of work for them. But if you take a stab and ask for feedback, that’s much easier.
> If you ask an expert open ended questions, you are creating a lot of work for them.
True, but my questions were pretty direct, and black and white.
> But if you take a stab and ask for feedback, that’s much easier.
That's true in that it's showing that I'm attempting to solve a problem, etc. However, for the scenario with this team, the work involved in answering was the same before and after. These weren't open ended issues.
The questions were typically "Should I do A or B?" Eventually, with no response, I'd announce "I'm going with C" where C is clearly wrong. I always then got emails telling me which of A or B was correct.
Oh, and I didn't ask for feedback. I learned that would not elicit a response. Just a straight up "FYI, this is the plan and I've begun execution." That led to urgency in responding.
No one could complain they didn't have a heads up as I often had weeks of unanswered queries to refer them to.
As I said: Crappy thing to have to do, but this was one team where more reasonable approaches just weren't working.
In real life you should mostly just remember to not be afraid to say what you think is true. If you are right then all is well, if you are wrong then it is good that someone helped correct and make you a little bit less ignorant.
https://www.urbandictionary.com/define.php?term=Cunningham%2...
Some think that internet arguments are a waste of time, they must either do it wrong or they don't realize how well it works. The most important thing is to not go into arguments you know you will win, you don't learn anything if you go through the same argument over and over so just don't do that and instead focus on things you don't already know well.
Also I don't feel that these arguments are off topic either, you learn a lot from just watching others argue, that is the main reason I prefer reading forums over reading articles, as the forum has people arguing with each other while articles are mostly just long monologues.
Depends how you view it. To me every statement every person makes is speculation or anecdotes unless they preface it with "factually" together with some reference or similar. That way conversation flows much better than when everyone has to preface everything they say.
But if its a negative experience or something where you are trying to actual support someone or relate to them in a time of trouble, then empathizing by expressing a similar experience is actually helpful. In the depths of grief it is nice to be able to relate to something, because in those times it can feel very very lonely.
Anyway, I am not saying the author is wrong. I think it's important to know the difference, but I am wary of the advice saying to never share your similar experiences in conversation.
By this criterion there are rarely any good questions asked at academic talks. The structure there is more like questioners firing tennis balls at the speaker who then tries to knock them back.
There are exceptions, and some good questions involve restating something the speaker said, and asking the speaker to expand on it or explain it in more detail, which they're usually happy to do.
A conference talk at which you are not allowed to voice criticism is not a scientific event, but a sermon.
Just, be a man. You will look like you know everything constantly.