Willingness to look stupid
danluu.com
danluu.com
I brace myself to be the idiot. I'm going to waste everyone's time asking questions that everyone knows the answer to, and I just got looped in, so everyone's going to feel like they need to walk through all the super-obvious stuff to satisfy the one guy who didn't do his homework.
So I start asking questions, and slowly begin to realize that nobody in the room has any idea what they are talking about. That there are fundamental misunderstandings and misconceptions about existing systems. And, naturally, it turns out that the questions I have are questions that other people have.
This has happened to me so often now that you would think the sinking feeling I get before I brace myself to look stupid would go away, but it never does.
In this situation I feel some anxiety or hesitation about asking these questions, but I don't feel it as a fear of appearing stupid. Instead the anxiety seems to come from worrying that I am annoying or offending everyone with questions about things that are obvious.
I have no way of knowing which question is going to reveal the problem, so I will need to shotgun questions. I know that some people that I work with get this completely and will cooperate. Others will get defensive or tune out, so I need to find a balance or tone to try to avoid that.
It is similar to when I did tech support as a teenager and someone would call with a problem, wanting a tech sent to their house. I would start asking questions about the problem and they would not want to spend 5 minutes going through a few steps to try to solve it over the phone. I never felt that they thought I was stupid, I just felt they were impatient. Maybe they did think I was stupid, but I was so sure that I could find the answer that I never considered that.
I guess I still work this way although I've fallen out of the habit of warning people and asking them to humor me.
Turns out I absolutely cannot do tier 3 support, but I can do 1 and 2 for friends and family and I'm the "whiz" or whatever. Tier three, for me, was basically me in a bad mood talking to me in a bad mood, in order to gatekeep the poor dev/DBA/NOC that had to actually fix things. No thx!
I am surprised at how difficult it has been to emulate her technique. Feeling comfortable asking the obvious questions is one half of the battle, but the other, more difficult half, is knowing what obvious questions to ask. Most of the time when I ask obvious questions, the replies are yes/no. She knew how to ask them in such a way that gets the person talking in greater detail.
It's kind of like being a great interviewer, there's a technique to asking questions in a manner which gets someone talking.
She’s big on that exact phrase of “this could be a really stupid question, but…”
She’s also really good about making sure other people are rewarded for doing the same by reassuring someone asking what might be a dumb question as, “that’s a a great question and I’m sure others were wondering the same…” before responding.
Great leadership, IMO.
This was great for two reasons: 1. it builds up large common ground for understanding; 2. if someone in a leadership position does this, others will not feel ashamed of asking questions that they think may be basic.
We were there to discuss a technical implementation.
She kicked it off by saying "Let me start by asking a simple question, why do we do this function?"
I am now considered a domain expert. I love this question. It surprises me at how few people start with the why, or even can articulate the why.
The room of experts, were assembled to roll out a new product in their area of functional expertise. None of us had an articulate answer as to the why. She kept on asking. She gently challenged bad answers with a follow up why. Then when everyone gave up, she gave her answer as to the why. It was brilliant.
Always start with the why. Then ask why again. Keep on asking until you understand why.
I always ask people why, because I sometimes learn something new, I often learn about the knowledge level of the other participants, and it anchors everyone to the fundamental problem we are trying to solve.
As someone who's recently been put in a position to make sure everyone's aligned (and failing quite a bit at it), it sounds like genius, in my opinion.
To stay respectful, it is polite to negotiate with all participants in its use.
When you already (think you) know the answer, then it's a pedagogical technique. That's ok unless you happen to be wrong about the answer.
(Though when I tried to use a causal DAG for root cause analysis of an incident at my current company, I was told that I was wasting time and no one cares. But I thought the data I found was pretty interesting and worth exploring.)
In manufacturing there is usually 4 big topics (person, machine, material, method), but there are many variations that can be used.
Trees or other visual depictions can be used too.
The point is to have some sort of structure and adapt it to your needs.
You keep asking "why?" and only want one 'thing' to be 'actionable'... you will raise my frustration level. The root cause is an emergent property of understaffing, poor communication practices and a belief that everything can be reduced to a jira card providing sufficient context and understanding for a diverse audience with different skills and needs.
It's really hard to do RCA when people are blaming themselves. It had to suck to be in that meeting. A really good RCA isn't about finding a single actionable thing, it's about finding our what the root cause of the problem is... which in this case, might have been whatever originally broke production and caused an emergency fix that failed three times.
Often, the root cause is someone made a mistake. You can say there should have been other systems to prevent/review/etc, but the root cause is a mistake a person made. You can '5 whys' it to death, but I made a mistake (or... someone did).
"whatever originally broke production" - in this case, I made a mistake. That mistake wasn't caught until production. Then the fixes were all broken too.
I don't always blame myself for everything, but if I've made a mistake, I'll own up to it. For me, it helps me be aware of what I can do to avoid those in the future. This may or may not be some rca-checklist other people can refer to, because... it's not 'actionable' to anyone but me.
I like it when they ask basic questions. at least then I can then explain the basics to them without having to feel like I'm patronizing.
Also, I just took a training and observed the trainer hear a participant say that she felt frustrated with the process, and then the trainer immediately asked the room something like, "How many other people are feeling frustrated as well?" And of course, numerous hands went up, and it seemed to help show the person she wasn't alone.
Dumb question here, but is it as simple as starting your question with "how" or "what" rather than "does"? The former invite explanation and the later looks for a yes/no.
My big thing lately is to not ask rhetorical questions (which can be sarcasm in disguise) as they either cause people to be defensive or simply agree. Either way they do not speak directly about the "obvious" problem.
Yes, this is the 101 of basic interviewing in journalism. Inexperienced reporters often ask too many "does" questions and are puzzled afterwards as to why the interviewee didn't talk much.
"Does" is also used when the journalist aims or pushes for a straightforward, yes-or-no answer. For example to interfere to a politician who is trying to avoid direct answers by trolling the interviewer with some off-topic agenda.
See also: https://en.wikipedia.org/wiki/Five_Ws
Also, this is a funny proposal with regard to the Five Ws: https://www.newyorker.com/humor/daily-shouts/additions-to-th...
I really appreciate that you used the technique that people were discussing and it still seemed to work here, at least it worked on me. I found myself thinking, "No no, that's not a dumb question at all and I feel grateful that you asked it!"
So, thank you for that meta experience :-)
Yes/no questions are the worst. But even questions like "What did you do?" aren't great because the answers can often be rather short.
A better question is often posed like "Tell me about X" or "Describe how you did Y".
Of course this isn't universally true, there is value in binary answers.
But often you may find yourself, let's say in a sales context, asking something like "What tool are you using for project management?"
The answer will then be something like, "I'm using Jira".
Instead, if you ask, "Tell me about what you're doing for project management on your team", the answer may be much more detailed.
"We follow the agile methodology and use Jira for our task management. We've got a dedicated project manager on the team who..."
Getting good at asking the right questions is worth the effort.
Better to have asked, "what's it like outside?" or, "what's the weather right now?"
and nobody is going to say it’s not raining when it’s hailing outside… but I understand if that was just a metaphor. You’re probably asking that question to figure out what kind of clothes to wear, and they would probably infer that. It’s so contextual though.
That also depends on the person. With some people open ended questions are great, with others yes/no are better.
I'll also add that yes/no questions are often faster if you get the response you expect.
Is it raining or something else outdoors?
Do you like Vi or Emacs or something else?
Do you want to hang out for a coffee or something else?
For the "Is it raining outside", I honestly don't know anyone that would just tell me "no" when there's hail outside. For the "Do you like Vi or Emacs or something else?", it would be "What text editor/IDE do you use? Why?". "Do you like Vi or Emacs" by itself is not a yes/no question, it's a "what box are you in" question. For "Do you want to hang out for a coffee or something else?", that would be something like "Do you want to hang out at <TIME>?".
An important part for me is that in yes/no questions, no are supposed to be the exception. In my mind, when I ask them, it's not a 50/50 chance. It's more of a 80/20. If it was a 50/50 chance, that means my mental model is not precise enough.
This is my approach when getting pulled into something. If I have no idea, I want to get that idea. I'll also use "this may sound stupid, but..."
One of the smartest people I've ever met in business was also this way. He also never nodded his head in agreement unless he actually understood and agreed. If he wasn't sure, he'd pause for a minute and work it out, even if it meant pausing the flow of the meetings. Some people interpreted it has him being "slow" but it really meant he actually understand all of the things he was nodding to.
Luckily, I've always been around coworkers that never put me down for asking those questions.
Most of them were illiterate and did not understand what plant scientists or professors were talking about re inputs or seeds or Tractors etc needed to modernize Ag.
So the format would be an interview in the middle of a coconut grove or a farm. The interviewer(usually female) would ask a question and the expert would answer. After he finishes answering, she’d turn towards the camera and go like “what you are basically saying is..” or “what he is saying..”..and she’d give the wrong details. Then the expert would interrupt her and explain it again with the correct answer. There were a lot of English words he’d use and she’d break them down in the vernacular and also in the same order as his sentence.
These wrong things repeated by her were obvious misunderstandings anyone unfamiliar with fertilizer application would make…it was probably scripted so that the answer can be ‘corrected’ multiple times and also probably reflected mistaken notions by the viewer. Never once was the viewer(here, it was the illiterate non English speaking village farmer) made to feel dumb but always as though they are learning something valuable and special.
It was like Sesame Street for farming adults. It was awesome and kept me glued to the television screen. I would memorize all the IRRI rice hybrids and probably was the only one in school who knew IR20, IR64 and IR8…and urea application rates for them.
Ask anyone of a certain age who their favourite Sesame Street character is …and you would have cracked effective communication technique for that time period.
When you active listen, even if the question might feel stupid, the feeling gets lost in the fact hat the other person is receiving your attention. This technique is also teach for other contexts like counseling, or debating using the Socratic method.
I have a weird job title but my position is probably closer to your PM, and I also use this strategy, so I'd like to know how to not annoy people!
I often ask these "stupid" questions, though. I usually start with: "it might have been said in other meetings, but just to be sure, what is...", "I might be a bit slow, could you explain X once again just to make sure I understand it", "So just to paraphrase what we've been discussing, X is Y, is that correct?", and sometimes I just ask "what does $acronym stand for and why is it important for us now".
I, too, often find that nobody knows the answers to very basic questions and we are in a meeting of 6-12 people...
I preface some of my statements with this, and I fully expect them to be stupid. In fact, many of the questions I ask that I don't preface with the above disclaimer are in fact quite stupid.
Asking fundamental questions in order to build up to a more complex understanding is the most effective way to learn, I have no hesitation about asking such questions.
It's better to just kick things off with naive questions or even use a bit of humor to disarm people, so they don't feel like they have to be "advanced" all the time.
The point is not that anyone with the same question should feel stupid; it's that I don't care if anyone thinks I am.
Whatever the case, there are more effective, more genuine phrasings to use than to literally invoke "stupidity".
Examples please?
I was thinking about:
"I'd like to ask some things that might be obvious to many of you: ..."
I use it all the time. Oftentimes they are stupid questions. Sometimes they're not, but generally that's when I'm not sure if it's a stupid question or not. And that's okay—the point is, it's fine to ask stupid questions.
I prefer to say things like "I'm not fully up to speed on this, so let's go back to basics/fundamentals for a moment", or "sometimes we're so focused on the details that we can't see the wood for the trees - let's take a step back and just run through it at a high level again".
With yours it's to easy for someone to switch off and not hear what you said because they think you're talking bullshit.
In two sentences you managed to cram in 5 idioms/phrases that are basically corporate babble.
Folks who are good at communicating can always keep everyone feeling engaged and comfortable, while still getting to nitty-gritty WITHOUT resorting to saying stuff like "... this is stupid question, but...".
If you think they're being disingenuous because you think they do understand what's going on, then it actually supports why they feel the need to preface their question with that phrase. You expect that they know it, so they make questions around it less jarring by admitting that they probably don't know enough.
It's important to treat yourself with respect, but people also respect when you admit that you don't know something simple.
I'm not sure what kind of audience you think it works on.
I tend to get (particularly from people under 40) one of two inappropriate reactions to reflexive self deprecation - either exaggerated sympathy for my plight, or treating it as an exposed weakness to attack.
Yes, some people will pity you, or treat it as a weakness. But having the courage to admit when you don't know something is a valuable trait that most people (in my experience) respect.
Also if you demonstrate your knowledge in other areas and contribute value to the meeting, people tend to forgive a few stupid questions in another area.
It's like when I'm having a meeting with my manager and I want to talk, so I start, they stop, I apologize for interrupting, and they say no, no, go on.
I assume there is no emotional drama going on. If they really want to continue talking, they can do so. That's why I apologize and pause. I'm not sorry, but I need to show appropriate deference.
It would be unfortunate if someone was building up resentment because they're not on the same wavelength about appropriate behavior. The purpose of etiquette seems to me to provide a formula to negotiate common situations without having to navigate emotional complexities.
But when different people have different rules, there's not much that can be resolved.
(Probably the questions aren't literally stupid, or the person maybe would never have been hired in the first place)
Sure...but I think that an insight that I've gained is that this is an example of a formula which doesn't really communicate or explain all the things you mention. You aren't sorry, you don't know that your question is basic, and you don't think you're wasting peoples' time.
In effect, it's a "pointer" to a bunch of things, so it only works with people that are conditioned to such things and have them in their memory. One of the things you mention, "not trying to school them" sounds to me like deference, and I don't think deference can be quickly established without a formula. Like a salute, you have to do something arbitrary in a mutually understood way.
I’m reminded of Arthur Dent (British) in the Hitchhiker’s Guide telling Zaphod, modestly, “oh, it was nothing” about something great he did, and Zaphod responding along the lines of “oh, it was nothing? In that case forget it then”, which was not at all what Arthur intended.
But being self-deprecating was not one of them. I feel like I'm surrounded by Zaphods, or something, and I'm not sure when it happened.
I ask questions that have a decent chance of making me look stupid all the time. Even when the rational part of my brain says "if you have this question, it's likely that other people do too," there's a big part of me that worries, "nah, I'm the odd one out here."
No, I often legitimately think that my question might (!) be stupid, because I'm aware that I'm coming into the discussion with less domain knowledge and experience than the other people in the room. I still think it's good for everyone (ie, not just me) to explain. (Sometimes it's clear that everything is just out of my league, in which case I shut up and let the meeting go on.)
I also preface with saying I'm going to ask stupid questions and if anyone holds it against me I'm ok with it. If I'm asking a question it's usually because I don't understand a consequent of something someone said that everyone seems to just nod their heads and agree with, and that gives everyone an opportunity to reconsider the fundamentals.
At my work, there's a bad combo of senior folks who whip off vague instructions in a single sentence, and junior folks who are afraid to ask questions. I'm in the middle, and I try hard to demonstrate that it's fine to badger the senior folks with questions, and to check in with them constantly. The senior folks like it because it gives them confidence that you're working it out. But some of our straight outta school colleagues just don't do this ("Gotcha. Sounds good!" is a very common email reply from them) and it leads to confusion down the road. After giving them the "ask questions" talk two times, I usually give up on them.
Also, in my position, I often have to review and edit reports that are largely written by electrical engineers and architects, and they all probably think I'm super dumb. I read the reports as the target audience (often non-subject matter experts), and so my comments are things like, "What do you mean by this [basic EE concept]?" I don't preface it with, "I know what this means, but the client might not, please elaborate..."
Does it help?
This sounds like they are expected not to waste time, so it might get even harder to ask a stupid question a minute too late, and especially to ask something tomorrow.
But you’re right that it might not be the best technique. I understand the hesitancy to ask questions after a certain amount of time has passed.
I work as a consultant and our time has to be billed to projects. The onboarding stinks, so the new hires often have no concept of billability/utilization nor project budgets. So I’m trying to drill in those concepts, too.
One of the additional lessons here is “the boss doesn’t always know what they’re talking about.” And that’s another hard one for them to accept. Question authority! If the instructions aren’t clear, then they might be nonsense. Have the guts to challenge the boss. And sometimes the challenge can come in the form of a million stupid questions.
As an aside, do you think there is a business opportunity in teaching companies better onboarding? Growing headcount seems like an afterthought most places, and it’s a colossal waste.
The worst example I’ve seen is one company hiring some very expensive onshore consultants to build the basic structure of the application and then quickly hand it off to cheap offshore ones.
What really happened is that the onshore guys created a horrendous mess of untested and undocumented code full of bugs that the offshore ones had no hope of making sense of. And being remote and from a culture of high power distance further exacerbated the problem. It certainly worked out well for the onshore guys who got to bleed the client out of a whole other year’s worth of expensive hours.
So, maybe. It’s risky, like you’ve demonstrated.
Something like this maybe: go to the new person, in the beginning every day, then once a week, then once a month, and say:
"Can you please ask three (3) basic questions about things you're slightly struggling with, and that you think everyone expects you to know, but that you don't?"
I like this because I feel like it kind of de-stigmatizes asking "obvious" questions. If you acknowledge that the the question might be redundant, but ask it anyway, I think it makes the dialog more approachable.
This is not easy to learn, and great understanding ability is a prerequisite.
inquisitiveness during problem solving is admirable and good, but in the article many of the applications of 'looking stupid' only serve to render the author untrustworthy.
“Just making sure I understand this correctly… stop me if I’m wrong” has worked wonders for my ability to contribute to a meeting.
I guess you might be asking straight up binary questions like - is it happening due to xyz? Maybe, changing the question format to something like - what do you think could be the cause behind _fill the situation here___? Just my humble opinion.
I've had similar situations, it feels analogous to group based "rubber ducking"... having someone ask the questions perceived to be known or obvious by the existing groups can be extremely beneficial for all kinds of reasons, in the same way that a rubber duck (real or imagined) will get you to re-evaluate all of your assumptions and usually get you to find the assumption that's incorrect or problematic.
This is debugging 101. You have assumptions about how a system works, but the output isn't matching those assumptions. You walk backwards over your assumptions and test them to see if they are true. Eventually you get to the precise place where your assumption is wildly different than the output, and there is your bug.
The more systems (or people) involved, the longer it takes, the more complexity.
In the spirit of doing less work, he proposed to me changing the meaning of "someProperty" to mean something different, without changing the name of that property.
Also, it was a boolean; so he wanted true values to actually represent false, and vice versa.
I politely pushed back on that one.
It happen for me once, and this was an humility lesson.
Now I keep in mind I can feel I understand the problem then realize later I was all wrong too.
I've been in other organizations (and even within this one) where my stupid questions revealed nothing new except that I had to go back and do some studying before I could usefully contribute.
I remember when I took a course in General Relativity as an undergraduate; I was much more math/CS focused than most people in the class, who were mostly physics people. And we would get together in study groups, and although I was respected for my general intelligence, it became clear that the questions I was asking were simply not the right ones -- that a physical/geometric intuition was something I did not have. In other words, I was actually the stupid one.
Much later I took a course in differential geometry, and eventually started seeing how it made sense mathematically, but I could never really connect it back to physical intuition. I think the problem that broke me was talking about the behavior of a point mass, and I had literally no idea how to attack that with the tools we had.
Personally, I don't really care about this second-order effect that asking such questions might identify others that don't understand the problem correctly. I think it's, as you say, creating its own bias that pollutes your thinking. I've worked with enough experts outside of my own domain expertise, that this is not something that happens often.
I have seen a few people unwilling to admit that they don't know...when they're supposed to know. The easiest way out they come up with is 'we will discuss this offline'.
Playing dumb, if you will, has served me well, yet it is also odd to me just how often it needs to be employed in the field of software.
Plenty of otherwise good things can be signs of dysfunction. An example could be a workplace where people are free to chill, do what they want, ride scooters, play games, etc., which can be really healthy and good for creativity, but also may be a sign of weak leadership and nothing actually getting done (wasting time and jeopardizing the future of teams). Having process is usually better than no process at all, but process can also waste time and be counterproductive.
In other words, nothing is necessarily to be viewed as good or bad.
This works and should be encouraged if you are indeed very smart and very quick, typically introverted and are actually going to be rolling up your sleeves to pitch in.
This approach is painful for everyone else and should be discouraged if you are a very extroverted and very non-technical person with no plan on actually helping out whatsoever with the actual execution on solving the problem at hand and really are only contributing to look smart in front of any leadership who happens to be in the room.
Definitely be aware of the Dunning–Kruger effect - which is a cognitive bias stating that people with low ability at a task overestimate their own ability, and that people with high ability at a task underestimate their own ability.
I brace myself. I'm going to waste your time. This is super obvious.
Here it goes: so uh, why do you continue to work with incompetent idiots instead of finding a workplace where people know what they are talking about instead?
Assumptions are inevitable. They get harder to question the longer they go unquestioned. Newcomers to a group can see them better.
Perhaps cutting people some slack and helping them work better by asking basic questions is a skill we all need to learn.
If you think so, alright then. I don't.
Everyone sometimes screws up. Some more than others. Some distractingly so, and some so often that it's not worth continuing the relationship. But the mere fact that someone at some point screws up does not make them irredeemable. So, yes, I think cutting people slack is important.
This is totally orthogonal to being qualified for a job, or being good, or any other attributes people have that puts them out of their depth. If you work with a bunch of unqualified poseurs, then sure, slack isn't what's missing, and you should quit. But if you find yourself in that situation very often, I'd be asking different questions...
And. What if it's your customer in the room? Are you firing them for being 'stupid'?
The superclever types that thing their colleagues are stupid are often the most dangerous, as they'll just 'go it alone' and then leave when they fuck up and suddenly everyone is stupid and not grateful.
I think it’s OK to ask dumb questions twice. If you don’t get it by the third time (or fail to remember), then we might need to step back and revisit fundamentals, or your mental model might need adjustment so that the information makes sense in context.
My favourite examples are things like "what is a user?" - the marketing department may be counting leads generated, engineers are thinking about records in a database table, some other team may think of users as company or group accounts.
This holds true for all kinds of other things too. You might have a project called "the login optimization project" and find that some people think it's about page load performance while others think it's about increased conversions.
For this reason, I'm always ready to ask the stupid questions.
I have spent far more time than should be necessary aligning on terms like "customer" and "user."
I'm grateful to my parents or whatever it was that enabled me to not take myself too seriously and not care too much about people thinking I'm stupid, even at work, and even though it may cost me dearly in terms of career progression. (because I do think not all but many people who get ahead do so by very successfully avoiding being perceived as stupid, even if they are)
It's amazing how frequently fancily dressed, well speaking, high paid people sit in rooms and essentially role play being adults while just having absolutely no clue what is going on.
A team I work with sometimes was blocked on a couple of PRs for about a week. I needed one of the team members for something and their lead wasn't doing much to help remove his roadblocks to helping me so I stepped in asking my really basic questions about what they were trying to achieve.
Within about 30 minutes we released one PR and deleted the other. The one we deleted was blocking the other but there wasn't actally a need for it due to some spec change that happened earlier, just nobody could figure out why it was needed or what needed to be finished before it could ship.
I don’t know what it is about the IT trade, but so many people seem to find it difficult to admit that knowing everything is impossible.
I can highly recommend reading, or listening to "Surely You're Joking, Mr. Feynman!". Asking "stupid" questions does not automatically make you intelligent, but it is a trait of highly intelligent people, exactly because of the reasons you describe.
We all know the story about how Newton asked why an apple fell to the ground, surely a lot of people would have thought you're a total idiot for asking that, and yet at the same time no-one would have been able to explain why.
The reason stupid questions are uncomfortable is that you're very likely to insinuate other people don't know the answer to a simple question, and we don't like making other people uncomfortable. Which is why you have to be humble when asking them.
Last question was followed by the longest silence I ever heard in a meeting... I wasn't invited the next meetings. I heard it took them more than 5 other meetings to reconsider my solution. An intern has finally been sent to buy the hard drive last week.
Maybe then they didn't want you in the meetings?
(Whilst the idea was good so that's what they did in the end)
(200 Go = GB I suppose)
There are ways to create roundabouts so that the solution looks “elegant” but only after “hard thought”.
There’s also the risk that the simple solution has some real limitation (eg. some regulatory issue) then you’ll will indeed look stupid
> I brace myself to be the idiot.
I don't think not knowing something makes one an idiot. Having hard time understanding something does. I don't think your example applies here.
(I’m not saying it’s a good thing)
My intuition has changed from this, I find it that most times, when someone shows genuine interest and asks honest, revealing questions about some new topic, they often excel at many other things (and will likely on the new topic as well).
I'm adapting this myself, being honest, asking honestly, and sometimes looking really stupid (because, in that context, I am!), and I appreciate greatly both the wealth of information that allows me to access, and that almost anybody worth their salt recognizes this trait as well.
Failing an interview due to looking stupid is probably a blessing in disguise, you don't want to be hired by people who can't see this, and you don't want to work next to people who's just pretending to understand, not learning because they can't afford to look stupid when they are (and thus stay stupid, and be much more inclined to try to pass blame to someone else, like you, who look stupid).
Naturally, the established powers and polite society didn't find this to their liking. We all know how his story ended.
> Naturally, the established powers and polite society didn't find this to their liking. We all know how his story ended.
Socrates was sentenced to death not for exposing how little everyone else knew. The esteemed philosopher was sentenced to death because he was deliberately annoying people - like a fly - with badgering questions that would force the questionee into a corner.Today we call this method of exposing contradictions in one's mindset the Socratic Method.
> sentenced to death because he was deliberately annoying people
I see you're still certain of Socrates' motives.
When you claimed he was 'corrupting the minds of the youth' and 'denying the gods of the city' you were simply repeating the charges laid at any philosopher who threatens the powers that be.
If anyone asks too many uncomfortable but honest questions these days, in some societies you will still be met with death, though here we have a milder but still harsh punishment known as 'deplatforming'.
But more to the point, if you are so certain of what you know, you could explain it and wouldn't find questions 'annoying'. Frustration justifies the case, because it means you really do know nothing but simply aren't honest enough to admit it.
Care to elaborate?
Just that it doesn't hurt points of view that are legitimate.
Illigitimate views and your feelings may still suffer from hearing the truth.
My point is that the facts don't care.
Therefore, completely true facts can make you believe a falsehood.
Therefore, the truth can harm a point of view that is legitimate.
It was a pretty big event so I know we all remember it as long as you follow current events, but it's easy to find articles mentioning it.
https://www.wsj.com/articles/cities-reverse-defunding-the-po...
https://www1.cbn.com/cbnnews/us/2021/february/minneapolis-re...
https://www.washingtonexaminer.com/news/portland-mayor-addit...
Cities defunded police departments, crime went up, some of those same cities then later re-funded those departments, and even increased budgets.
The crime statistics and city council laws passed support these claims, I have not found any claims disputing these facts.
Even the left most leaning sources agree with these claims.
The police budget for MPD in 2014 was $145.6M for 850 officers. In 2020, the year you suggest they were defunded, the budget was $181.9M for 770 officers—a 38% increase per officer from 2014 (28.7% after adjusting for inflation)[0]. In fact, that department is ending the current fiscal year $5M under budget[1], and the current mayor has proposed an additional 17% expenditure increase for 2022.[2]
The police in Minneapolis were never defunded. They have more money than ever. Efforts to introduce meaningful reforms (inaccurately called “defunding the police” by some) have also not been abandoned by the city council. We are currently voting on a charter amendment that would replace the Minneapolis Police Department with a new Department of Public Safety. The new department would still include police officers but would be coequal with all other departments in the city (it currently has a unique status where it is controlled exclusively by the mayor), and its focus would be on preventing crime instead of policing people.
On the other hand, other parts of the city budget are underwater due to hundreds of former officers quitting and claiming PTSD[3], and the officers who remain are engaged in an intentional work slowdown[4] while blaming others[5] for what is a largely self-inflicted wound.
What I think the other participant in this discussion was suggesting—and something that I would echo—is that your sources for news don’t seem to be giving you accurate information and you may want to reconsider using them as primary sources, at least on this topic.
[0] https://minneapolismn.opengov.com/transparency
[1] https://twitter.com/lisabendermpls/status/145018398771290931... (This is the Minneapolis city council president)
[2] https://lims.minneapolismn.gov/Download/FileV2/24988/2022-Bu...
[3] https://www.mprnews.org/story/2021/10/06/mpls-police-ptsd-cl...
[4] https://www.reuters.com/investigates/special-report/usa-poli...
[5] https://minnesotareformer.com/2021/10/20/mpd-cop-says-office...
February 2021, the Minneapolis city council voted to add $6.4 million to the police budget. [2]
[1] https://www.msn.com/en-us/news/us/minneapolis-city-council-v...
[1] https://www.nytimes.com/2020/12/10/us/minneapolis-police-fun...
[2] https://www.msn.com/en-us/news/us/minneapolis-to-spend-2464-...
The budget for 2020 was never in question, the riots and defund police movement started in the summer of 2020.
City policies were being discussed late in the year, concerning the 2021 budget.
Less resources means slower response times or no response at all.
That wasn't the premise though, the question was whether they defunded and then later refunded when crime was rising.
Above I showed GP that Minneapolis did in fact do this, as did many other cities.
https://www.dailymail.co.uk/news/article-9625629/REFUND-poli...
So they didn't actually do anything.
Some cities backpedalled on their promise to defund and added to the budget instead.
The existence of the latter scenario does not nullify the former.
[1] https://blog.youtube/news-and-events/managing-harmful-vaccin...
Merriam Webster has used that definition since they added the term to their dictionary in 2018: https://www.politifact.com/factchecks/2021/may/17/viral-imag...
Though I do like your form of expressing your frustration about the trial and sentencing of Socrates at myself as though I were his prosecutor, I assure you that I'm an under-50 mortal not born of gods and not atanatos.
> you could explain it and wouldn't find questions 'annoying'.
A question would not be annoying. Badgering, accusations, and pestering would be. And quite frankly, as we both know, every single one of us has contradictions in their beliefs and their actions. I'm not going to defend mine in public to a beggar following me around with the explicit intention of exposing my contradictions to my peers as a way to demonstrate that I (and for that matter, anybody) am not fit for the office I hold.So yeah, "different set of ethics or starting to distrust authority" but no necessary in a nice way.
Of course you do, you just wait until you have a more ethically "usable" argument than that, you build a solid case, then you have a mock trial and a fully expected conviction.
It was as true 2500 years ago as it is today.
It had more to do with revolutions in city just before, when two his students and friends worked with enemy to make dictatorship out of Athens. They killed and tortured quite a lot of people. Then it reversed. Now, he did not participated actively and citizens behavior during above was supposed to be forgiven anyway. It was miscarriage of justice.
But, these events in combination with what his ideas actually were were closer to why they wanted him killed then general "asked too many questions". As far as they were concerned, he was actually dangerous.
The yet other official reason was impiety, which despite sounding ridiculous to us, to them was important too.
And I dunno, ask my wife.
The two are not mutually exclusive.
No. Socrates was executed because he was associated with the worst rulers that the city of Athens had ever known, all former students of his, who notably went on to kill thousands of Athenian citizens (not enemies, strangers, or slaves), following the defeat in the Peloponnesian War.
After the tyrants were killed and democracy was restored, general amnesty law was granted to anyone involved except the Thirty Tyrants themselves and their direct aides. However resentment, understandably, remained.
> There was a lot of bad blood between the people of Athens and Socrates’ followers. That wouldn’t have been enough by itself. But the murder of between 5% and 15% of the citizen population in 404 must have pushed things over the edge. Imagine if Osama bin Laden, Timothy McVeigh, and Saddam Hussein had all had the same person as their ethics teacher: would you be very surprised if that person got harsh treatment from a jury? And would you then call that person a martyr?
http://kiwihellenist.blogspot.com/2016/04/socrates-1-did-soc...
I guess there's some platonic happiness in thinking you have it all figured out.
error 404: population not found
i like the term abandonment these days, drop your assumptions, drop your habits and try to see things as they are
When trying to approach sacrosanct 'truths' from a clean slate, I've met torrents of emotional resistance. Yes, from others. But also inside myself. It is quite something.
I wish I could spend my days wandering the marketplaces asking sincere and pointed questions, but I have to get back to work.
“Nothing to excess”, and “Certainty brings insanity”.
Imitation, which is easiest.
Meditation, which is noblest.
Experience, which is bitterest.
Anytime I learn anything new, I imitate until I can’t anymore, then I meditate to understand why I think I can’t imitate anymore, then I experience my meditation, then I go back to mediating based on that experience.
Repeat until you can’t OODA loop effectively anymore.
The environment largely shapes people's behavior. Of course, we can argue that we should work towards changing the environment for the better, but practically, how much influence does a person (who is not in a position of authority) have? In the end, people simply take the easy way out, which is keep quiet and only speak when they're absolutely sure that whatever they're about to say/ask is fully accurate.
Surprisingly much, for the kind of people who stay quiet. They underestimate their own potential impact.
I certainly remember feeling that way when I was a junior engineer. It was kind of a shock to me when I realized how many others generally had the same questions I did.
conversely, when interviewing or evaluating people, if i observe someone pretend s/he knows something, that's often a really bad sign…
I've never inferred stupidity or lack of intelligence with asking questions. The only thing I've inferred was lack of knowledge. And the best way to get knowledge is to ask. People who ask want to know. They want the information to get to correct.
People who don't ask questions eventually make assumptions that are wrong. Because they're so wrapped up in "looking smart" and they think being "smart" means having all the knowledge. They "want to be right" so they don't look information because looking would expose they don't already have it.
Smart people seek information so they can apply it. Genuinely intelligent people just have faster processors.
What I take from the article is that saying stupid things is the best way to avoid doing stupid things.
The issue with this is that you might not even work with this one person declining you.
The causality also goes the other way. Very smart people see their limitations more clearly and so tend to be humbler about what they know.
They realize they can learn from others and so ask a lot of questions that others might feel foolish asking.
However this only works when there is enough knowledge to know why the unimportant details won't matter.
It's happened to all of us though we dont like to admit it.
I'm sure it's happened to him too and I looked but I didn't see any of those examples listed.
Giving only examples of when people thought he was dumb and it turned out he wasn't... that's kind of just a roundabout way of humblebragging that you're an unrecognized genius.
Sadly I think this undermines the point of the article which otherwise makes a good point.
It is a justifiable fear. For example, it is easy for people to interpret an imperfect amount of courage as "humble-bragging".
I thought it was heavily implied from the way the article started that we'd be reading some embarrassing stories.
I was somewhat disappointed to see that he was presenting himself as just a humble genius who thinks different.
There's distance between:
"people think I'm stupid because I'm not scared to show that I don't know about something"
and some of the examples which are more along the lines of
"people think I'm stupid because I act as a self-entitled genius who provides little context or reasoning behind choices and expect everyone to line up behind with no question"
What is the Apple store employee supposed to do to not make someone feel stupid when they ask for the smallest box? What are the chances they're not a clueless customer in need of help and have solid reasons behind?
The boss raises an eyebrow when someome proposes to skip half of the test suite? Means a lack of trust.
The insurance dealer does his job and tries to get a higher premium? Not surprised.
There's quite a bit of narcissism here: "They though I'm stupid but I'm not", " I was right in the end". It's actually arguing how everyone else is dumber in the end.
A more sincere approach would have been to explain how he realized how stupid he actually was and how not being defensive about it helped. But perhaps the author knows better after all.
Maybe ask the customer, “can I ask why you would like the one with the smallest box?” instead of making assumptions? Although note that this might also be classified as a question where the person asking is admitting they don’t understand why someone would want this aka “looking dumb” in the wording from the article
That last one makes the most sense, and explains why he didn't divulge it. That way, when the author is raided, they aren't going to ask, "hey, where's that computer that, comes in the smallest box?"
I'm imagining the author has this big book case, and one of the books is hallowed out and has an Apple machine in it. Maybe it's built into a false floor of a cabinet.
I don’t why the author needed a small box, but I did think of my experience when I read his anecdote. I think a large part of his appearing impaired is not even attempting to explain his rationales, suspicions or methods in the moment. His goal seems to be to engineer these awkward interactions, when they could be otherwise lubricated or alleviated. He’s acting as though other people and their understanding are irrelevant to him; they are furniture or fixtures that should trust and obey unquestioningly, which is a bit ironic.
I read his post to the end looking for the answer to why he wanted the smallest box, furiously thinking of why. I could only think of three reasons that I rejected as unlikely. Frustrated, I came here to look at the comments. So many comments about the box. It's like the contents of the briefcase on Pulp Fiction. It's like a McGuffin that forces everyone to talk about his article.
It seems to me like he puts some intentionality in attempting to look stupid and a sort of satisfaction when this happens.
So his thesis is also that stupid people assume that intelligent people are stupid. He considers himself more intelligent than those people.
I wonder if he would be as willing to look stupid in front of people that he considers as intelligent as him.
It sounded to me like he was saying: I am willing to look stupid to people that I consider inferior (dumber than me).
I think this is the impetus behind the whole 'crawl, walk, run' thing. If you're always hot to trot and pushing an image of "I know everything already and I don't need to ask basic questions", you're never going to build the foundations of understanding necessary to construct more complex understandings.
With his COVID action— people disagreeing with him, at first, wasn't what had serious health consequences. He said he started wearing N95s several days before the initial r0 estimate was even published, and that he based his opinion on SARS-CoV-1 data which many relevant experts didn't think was applicable. There's a reason they didn't jump to the same conclusions he did, and that reason is why they're experts. He essentially won a bet talks about it like he figured out how to beat poker.
And if he recieved a torrent of negative feedback for his penchant for air filtering in 2012, that says a lot more about his friends and family than his very not radical adoption of home air filters less than 10 years ago? The whole sick building/mold aversion/exhaust fumes/smoke/spent cooking fuel/etc realm of AQ concerns has been a publicly accepted health concern waaaaaaaaaaaaaay longer than 2012. Sharper Image was making a mint off of their Ionic Breeze air purifier at least a decade before that.
Like I said, he's obviously a smart guy, but this whole 'they all laughed at me and look at me now!' narrative is just not that impressive.
I'm not sure why you're painting him as having psychological issues based on a blog post.
> He said he started wearing N95s several days before the initial r0 estimate was even published, and that he based his opinion on SARS-CoV-1 data which many relevant experts didn't think was applicable. There's a reason they didn't jump to the same conclusions he did, and that reason is why they're experts.
The same experts that were telling the public that masks were useless in March 2020. Experts are not always giving the best recommendations for your specific case.
> Like I said, he's obviously a smart guy, but this whole 'they all laughed at me and look at me now!' narrative is just not that impressive.
That's a very uncharitable way of interpreting that blog post. I personally see it as "next time you feel too stupid to do something, think about that blog post and maybe I'll give you the strength needed to do something that will have a good outcome".
Sure, there was no public data on r0 and no proof that COVID19 was similar to the other SARS viruses. But given only the info of "Wuhan was under lockdown", wouldn't it be indicative of the seriousness and the contagiousness of the virus, at least in the eyes of Chinese government officials?
I always thought the "West" misinterpreted the events in China at their detriment. Perhaps they assumed that it merely reflected the inability of the Chinese government to control a pandemic instead of actual seriousness of the disease?
Anyway I started wearing a surgical mask regularly and made sure I washed hands thoroughly after the Wuhan lockdown was announced. I hate wearing masks but it was less than $1/day and some inconvenience compared with an unknown but potentially scary disease. Not sure how anyone would come to a conclusion that taking precautions could be a bad bet (on a personal level at least).
Ebola was a large and growing problem in Africa in 2015 which covered a larger swath of the population, had nearly identical messaging from the Government, and would trigger a lockdown in Sierra Leone. Lots of folks regularly travel between the west coast of Africa and major American cities. I'd argue it would not have been prudent to start wearing Ebola PPE at that point, either. Of course, because it was Africa and not China, it only got marginal news coverage compared to the enormity of the problem on the ground, and much less traction on technology platforms because to this day, 25% of Sierra Leone's population has internet access. Epidemiologists were every bit as concerned about Ebola as they were about COVID before COVID's higher initial R0 number was released.
I'd like to hear the justification for not donning Ebola PPE given what was ostensibly a nearly identical situation that fortunately ended up being handled a whole lot better. Or maybe he did and he left that one off?
Seems he glommed onto the mask because it was something an individual can control in the face of an ultimately nihilistic reality, over which one has little influence. Like buying toilet paper despite assurances there is no shortage, myopic assertions on the observable sure seems to make people feel better. Speaking of shortages, the criticisms of n95's stemmed from a legitimate shortfall among medical personnel, despite questionable value to panic-buying consumers. "The Science" I'm sure he cites behind this rationale has been pretty clear regarding how Covid spreads. Prolonged close indoor personal contact. Wearing the n95 at the grocery store or while walking the dog poses little benefit because those situations pose little risk. Given serological investigation puts the rates of asymptomatic infection anywhere between 10 to 40:1, his roomie is more likely to have contracted it from him than from her unwillingness to wear a mask. Possibly while sitting at the dinner table with our author, rolling her eyes as he urgently espoused the virtues of the public N95. We'll never know for certain, but he'll surely continue to conversely reason her disagreement on the matter led to that, "stupid" conclusion.
Given the clarity of hindsight, global epidemiological statistics remaining largely unaffected by public mask policy starts to makes sense. After all if his reasoning behind the mask had an air of truth to it you'd be able to observe at least some impact on infection rates before and after mandates. Yet for the most part communities all followed a the similar bell-shaped trajectory, regardless of policy or political orientation. I see a lot of people pretending this isn't the case, that there isn't two years of data suggesting otherwise, meanwhile the rest are quietly bartering with their gods the others will get over it and move on with their lives. It's really a shame his article blundered into Covid territory, because he was starting to say something worthwhile. Like most conversations Covid, the substance evaporated as we were left with largely emotional appeals. Shame we can't talk about politicized risks pragmatically, trying to fit them into a wider context of facts and numbers. Like, why am I even talking about Covid when upwards of 8M people, largely children under 5, die every year from respiratory diseases caused by pollution? Sure seems the world has other problems. Maybe, like politics and religion, the topic just isn't suited for polite company.
This is actually an example of where the author IS stupid. You will often be found "at fault" in cases where you are not actually at fault (the other driver lies better than your truth) and there are many cases (at least in Ontario) where you are legislatively at fault even if you did nothing out of the ordinary (making a left turn while overtaking traffic attempts to pass rather than yield). That the broker was trying to protect them from this isn't even a conflict of interest for the broker.
I wonder how many insurance brokers encounter the "I'm such an amazing driver, I don't really need insurance." macho man ... I'm presuming the broker, at least initially, assumed the author was one of "those drivers" and not "stupid".
But that's where I see a problem: this (or another reasonable thing) is not something that would take long to explain.
Looking stupid is a failure of communication. You're right, but you failed to give enough rope for others to follow, and that wastes everyone's time.
The improvement I'd suggest is to dig into why someome thinks you look stupid. You could think "they must be stupid", but that, in itself, is an overly simplistic and inefficient model.
However, sometimes, for some drivers, fully comprehensive insurance can be cheaper than 3rd party only for arcane internal insurance risk-accounting reasons. So by not letting his agent even look at the whole market he was cutting himself off from the possibility of cheaper insurance.
The entire business is heavily regulated and based on accurately accounting and pricing risk. It seems suspect that a regulator would allow such an obviously mispriced insurance product.
All insurers have to go on to gauge your risk are the signals available to them & the type of insurance you’re buying is a signal.
Whether this is still true in the modern world I don’t know - I probably saw this advice ten years or so ago on a well regarded money saving site.
It would greatly surprise me if buying comprehensive insurance itself served that good of a signal to offset comprehensive/collision insurance for say, a $20k to $40k car.
This was regarded as a weird corner case even then & was mostly just used as an example of why you should try tweaking various features of the insurance you were after, because the price could sometimes change in ways that might seem counter-intuitive.
What I think you might be confusing this with, is that one piece of the insurance is cheaper if you bundle it with others. That is, liability-only might be $50, but if you if you get liability + collision, it's $80, which breaks down into $40 for liability and $40 for collision. The insurer is taking more liability -- but also more revenue, so no funny business.
The "high-risk poor" can't "cheat" here because they can't afford the extra $30 to begin with, and "being willing/able to spend $30 just to be safe" is an actionable signal of being low risk.
But you still shouldn't have a scenario where you get strictly greater coverage for strictly less money.
The insurance company now has no responsibility to repair the insured vehicle so they have less responsibility.
I suspect Collision insurance is very profitable compared to liability.
I expressed surprise that collision/comprehensive + liability can be cheaper than just liability alone, since, on the face of it, the insurance company seems exposed to more losses due to possibly having to pay the insured for their car damages.
In my comment, I wrote liability referring to the insurer’s liability for paying to fix/replace the insurer’s car, not liability as in auto liability insurance where the insurance company pays others for damage you cause to them.
Also, skipping collision happens most often when driving a really cheap car, which can be a marker for a bad driver.
Actuaries actually have numbers for this things, but I am just speculating.
It's a proxy for not being able to afford to fix or replace your car at the drop of a hat.
>Also, skipping collision happens most often when driving a really cheap car, which can be a marker for a bad driver.
Once again, just a proxy for money.
This also checks with the OP in this subthread: The insurance seller will always push for more coverage for self-interested reasons.
(I didn't go through with it on the call and maybe she would have put up resistance then, so who knows.)
Edit: From reading the source, it seems like the author didn't clarify that that was the logic he was using, or that he could afford the damage to his car out of pocket. Insurers are probably accustomed to people overextending themselves and skimping on insurance without being able to afford such things, which is risky and something agents have to head off early on.
Some will try to milk you for all you're worth. Others will try to stick to things that you plausibly need and hope that selling to more people and having a higher renewal rate will make up for the extra amount that they aren't squeezing out of each person.
As I understand it, Dan wants to skip on collision / comprehensive, not liability. I can imagine a number of scenarios in which you might not want to bother insuring an asset, even as you insure yourself for damage to others you might be at fault for.
Liability - that pays for damages/injuries to others
Collision/Comprehensive - that pays for damage to your car
It sounds like the author wanted Liability but didn't want to pay for Collision. If you have significant assets and/or a cheap car, it may be to your advantage not to get the collision. Except he didn't use the customary terms but described them rather elliptically.
In fact, take the money you save on Collision and get more Liability is not a bad idea.
Insurance is always a trade-off of EV for tail risk. In exchange for losing money on average (the insurance company has to earn money somehow, after all), you're protected from the worst case scenario. You can think of it like, yourself from parallel universe where you don't get into a crash, pays yourself in the parallel universe where you do get into a crash. And the insurance company skims a little off the top as payment for the service of sending money across parallel universes.
But if you can afford to just eat the cost of a crash, you don't need to pay the insurance company for that service. And maybe you can eat the costs of some crashes but not others: If you crash into a rich guy's car, maybe you can't afford those costs, but damage to your own car is capped at the price of your own car. So that's all Dan's doing: insuring the costs he can't pay (damage to others) but not the ones he can (damage to his own car).
The math isn't affected by his chances of being found at fault, or how good of a driver he is, at all.
$100k for coverage on your car? No thanks. $1? Sure. $1 but covers litterally nothing and has a million dollar excess? No thanks.
Another perhaps relevant thought, which is perhaps crass: If PG or Alan Kay ever claim that they are willing to look stupid, I feel like people would not believe them. On the other hand if Feynman does it, people would feel the sincerity. (At least the version of Feynman Feynman marketed, not the Feynman who couldnt suffer Gellman)
Another thought: maybe its better to be willing to look immature.
In this case, the article is not about 'the joys of being too dumb to breathe'. It's about how 1. looking stupid is not the same as being stupid, and 2. looking stupid can be beneficial in the long run. The author does not need to actually be stupid once in order to support this idea.
And I have to worry if you think he's "bragging" about merely looking stupid, as if that weren't bad enough. Maybe if you identify as stupid I could understand the offense.
To the author, Dan Luu: I like your article and I think you're on the right track!
Particularly in interviews, what I'd like to read is a reflection not on how to avoid thinking in the way that results in saying or asking things that sound stupid, but how to keep the same internal process without communicating the results in a way that confuses quite so much.
An analogy: a mathematician proves a non-obvious theorem. In their proof, they skip so many steps that it looks like they say intuitively wrong things.
It is NOT that they should stop thinking of these proofs in the same way, it's merely a failure of communication.
That’s the point being made here: not that his examples are wrong, that they are cherry picked to support his views.
It may be superficially thought provoking, but it is not compelling as a logical argument.
There are tangible downsides to ignoring expert advice; you are not a god. You cannot be an expert at everything.
It is not possible to be an expert at everything.
Therefore, yes, asking questions to understand a topic is good, but no, ignoring the advice of an expert is not good.
The examples given only show examples where the result of ignoring the expert, or third party advice was positive; it can’t possibly be true that this can be the case in all circumstances, except by sheer good luck.
I whole heartedly agree that asking questions is more important than looking smart… but:
> Overall, I view the upsides of being willing to look stupid as much larger than the downsides. When it comes to things that aren't socially judged, like winning a game, understanding something, or being able to build things due to having a good understanding, it's all upside.
You don’t have to look stupid to be able to do all those things, you just have to be humble and work hard.
This is a really nice, concise way to make the point you are making. Doesn't it seem like this is the central problem with politics today? Everyone has their own data and everyone is logical. You can't have a functional discussion under such scenario. People don't see any problem with their own logic because there isn't any. People can't definitively show a problem with the other's logic because there isn't any.
If the person actually is an expert, yes. But actual experts, at least outside hard science domains where we can run controlled experiments to nail down theoretical models to the point where the actually do have high predictive accuracy, are much rarer than most people suppose.
For example, the author says he ignored his doctor's advice; but that only counts as ignoring the advice of an expert if his doctor actually was an expert. Most doctors aren't--in fact, one could argue that no doctors are, since nobody has a really good predictive model for medicine. Many doctors know more than at least a fair number of their patients do, but that's a much lower bar to clear than "actual expert". And given the current state of medicine and the availability of information online, it's pretty easy for a reasonably intelligent person to know more than any of their doctors do about their own particular condition--since they both are more interested in accurate information, and have more time to devote to finding it out.
If the car insurance salesperson disagrees with you, maybe you should try to understand why? Did you really consider the possible that a tree branch could fall in front of your car or that you could get caught in a hail storm?
If the Apple store employee doesn’t understand why you’re obsessed with box sizes, explain that the MacBook in the smaller box is the one with the features you want and that’s the easiest way to identify it.
If someone gives you a look like “you’re stupid” it’s most likely that they don’t understand your decision not that they think you have an inability to reason. Sometimes you simply need to explain yourself, but it seems the OP has such confidence in their own decisions that they won’t accept any help or input from even the experts. After all as you noted, it appears that the OP has always been right in the end.
I hate this, the idea that I should have to explain myself to a random stranger in a shop as if they are entitled to know anything about me. I buy a lot of sweets on Friday for the weekend and regularly the clerk behind the till will make a comment, "Thats a lot of chocolate! Who is going to eat all that! You must be having a party whats the occasion?". In front of a line of customers who are eager to get home I have to explain myself to the clerk "Im depressed!"... and then just stand there awkwardly waiting for them to finish doing their job.
I get it they are just trying to be friendly but I don't want it no one in the queue behind me wants it, no one wants to explain themselves to a stranger we will never meet again, I just want the sweets / laptop please and thank you.
Even though I, personally, feel the way you do, the above doesn't ring true. Many people crave those small interactions with strangers, and welcome the opportunity to talk about themselves. That's the reason they're a social norm.
You sound like someone who has never worked in any customer facing position. Many people come in wanting X. They don’t realize X has many consequences. You know if you just give them X then they’ll come back another day, leave a bad review, or say, “but why didn’t you tell me this?!?!”
I mean, ffs - this happens to me as a customer and I’m thankful. Sometimes there are obscene arcane scenarios that you can’t find out about through regular means that only that service rep will know about. They are mostly fine if you just explain what you’re doing - they’re safe guarding the company’s reputation. They have nothing against you asking for weird shit - they just don’t want your bad shit later.
So you walk into the Apple store, walk up to an employee and when confronted with the question "How can I help you today?" what do you do?
Telling them "I would like X", seems like an unneccesary level of "explaining yourself". They should just know and understand exactly what you want from non verbal signals?
Very annoying, I want X thats why I asked for it, I dunno if I want Y because I didn't spent time researching it like I did X. I want X not an argument there are lots of other place I can buy X if you are going to be difficult about it.
He sounds more like my mother in law than like a keen philosopher.
Learning isn't a straight path. It's unusual to not veer off and misunderstand something for a while, during which time others might be right to assume you are "stupid".
The willingness to look stupid will sometimes reflect that you are, in fact, actually stupid. A lack of any examples in this category makes this post read more like a humble brag.
and this is why this article is popular. Everyone has to deal with looking foolish or telling a doctor they know their body better than them. I think playing it up this way and in this format really sells this idea of being this underappreciated genius in a sea of stupid people, which unfortunately a lot of people relate to, instead of attacking the social and systemic issues this person is actually experiencing. For example, poorly trained and non-empathic nurses or mask disinformation early during covid. Obviously these things are strongly liked to ruthless for-profit healthcare and how the right has politicized covid.
Most of the examples are bizarre. The air filter thing makes no sense. Its extremely rare to develop asthma in your own home because of being near wildfires. So there's no evidence his filters did anything. Also most of these are just being over-sensitive at not looking 100% competent all the time. Being bad or silly at videogames at first? That's a universal experience! Being right at work while others are wrong or lazy sometimes! That too. Doing the right thing when no one else is? That's universal too!
And like you said, they don't list the times they made a big seemingly merit-based action but ended up just being wrong.
This person just sounds socially maladjusted and probably suffers from a certain level of social anxiety. If they think acting normally is constantly making them look stupid, there there's something going on with them mentally that isn't healthy. Worse, it may reveal how they see others who aren't competent in the moment, which is really unfair to them. Does this person see us as stupid when we do everyday things? I suspect they do.
So the real take away here isn't "btw aren't we all geniuses if we're like this," I think he was aiming for intentionally or not, but a lesson on being tolerant of others who may not seem competent in the moment.
Lastly, this obsession with who is and isn't stupid is really unhealthy. I see it in a lot of tech people, and its just an ugly form of toxic masculinity. These people will mock sports people for being traditionally over-competitive, but don't see it in themselves when they do it in regards to smarts.
The unusual level of hostility the author encountered didn't seem right... Like you said, there's some over-sensitivity, a lot of jumping to conclusions, and hostile thinking from the author himself that led him to believe that so many people thought he stupid. Definitely some social anxiety in there as well, which is fine, but letting that turn into hostility is not.
It's a shame because the articles overall message isn't bad at all. Have the willingness to feel stupid for personal improvement is good advice but he just comes across it the wrong way.
This is not "willingness to look stupid", it's obviously the will/need/want to look mysterious to stroke one's ego.
He could have chosen to behave like a good human and say why he wanted a smaller box so no one looks stupid (he to the the employee and the employee to him) and even give some new insights to the employee to help another customer with the same needs.
> The person who helped me, despite being very polite, also clearly thought I was a bozo and kept explaining things like "the size of the box and the size of the computer aren't the same". Of course I knew that, but I didn't want to say something like "I design CPUs. I understand the difference between the size of the box the computer comes and in the size of the computer and I really want the one that comes in the smallest box", but just saying the last bit without establishing any kind of authority didn't convince the person
> I eventually asked them to humor me and just bring out the boxes for the various laptop models so I could see the boxes, which they did, despite clearly thinking that my decision making process made no sense
Oh c'mon, that's not fair. You have to tell us what the goal was. :) I'm super curious what a CPU designer wanted with the "laptop that came in the smallest box."
Perhaps smallest box = smallest laptop = they wanted to study the form factor. But does the smallest laptop really come in the smallest box? And did the results of this experiment influence your future CPU design decisions? I feel like this arc deserves its own page.
Without any kind of prior on this person's intelligence, I too would, in the position of the Apple employees, gravitate towards the "moron" theory.
Not explaining is just playing games at that point... Like morons do.
It raises even more (admittedly pointless) questions, like "Is that true for Apple laptops, or all laptops? I bet Dell packs their tiny laptops with a bunch of peripherals or padding. A larger box might get sold more frequently."
And even for Apple, are the boxes physically smaller between different models? I unpacked an M1 MBP the other day and was surprised how large the box was compared to the laptop. I think there's a 13 inch and a 15 inch, and it almost seemed like the box was designed for the 15 inch.
Hmm... This calls for an empirical study. Too bad I don't live across the street from an Apple store anymore, or I'd just go look.
But "How could any of this possibly matter to a CPU designer?" won't be so easily resolved. E.g. even if it's true that the smallest laptop comes in the smallest box, why didn't they ask for the smallest laptop? The salesperson would've been like "Of course, it's right over here." It sounds like he compared the actual sizes of boxes, which is fascinating.
It's clear OP _wants_ to illicit this feeling of superiority from others, as even after the fact - and with unlimited time and space - they do not state the actual reason.
Hypothetical time:
Let's say we have some reason to want to buy the laptop with the smallest box. We'll say it's some reason so incredibly intellectual we could never explain it to anyone else because everyone else is so much dumber than we are.
So, the best we can do while remaining perfectly honest is simply state we have this desire. Actually explaining it will either not work or cause the apple employee to turn in to a black hole.
So, we stand around asking them like an idiot for the laptop with the smallest box, which we know is easily misinterpreted, but for no reason at all we feel like we must remain perfectly honest. This creates a back and forth as the employee - predictably (especially so to someone of our amazing intellect) - tries desperately to help us see our error in thinking.
The whole process takes much longer and has been unpleasant for all involved.
But hey... at least we got to feel really smart?
Rubbish. The actually smart thing to do is to come up with a plausible reason for the stupid request. It's not even hard.
"This is a vanity gift for my rich employers spoiled kid, to unwrap in some stupid status showcase. None of them understand computers. I know the request is stupid, but let's just get it over with. Can you show me the smallest packaged laptops please?"
There. Nobody's time is wasted.
There is a difference between a willingness to look stupid in order to achieve your goal, and a desire to look stupid while enjoying being a conceited "smart" person at the expense of achieving your goal.
I work at an advertising agency if we buy something for a giveaway we care a lot about the box it comes in, not whats inside it as we will never open it. The person buying the laptop is probably a currier that knows nothing more than to buy a laptop. If the currier is getting interrogated by a 16 year old sales clerk thats costing us money and more importantly time.
I get they are just trying to be helpfull maybe even trying to save us money, but we only ever use retail because shipping takes to long. For example we have 20 laptops being shipped but need to take a picture of the box for promo material, we will happily pay for a new laptop and curriers simply so we can get a box in front of a camera so we can meet our dead lines.
If we spend £2k on a new laptop and curriers just for a picture thats money well spent if we meet our dead lines. If we miss our dead lines because some kid was trying to save us £100 its going to cost us a fortune / client.
"The customer asked for the smallest box so I assumed they knew what they were doing and sold them that."
"No, I didn't ask any further questions, I wouldn't want to assume they were stupid. That would be wrong in this narrative."
"No, I don't know how exactly how much $$ Apple is going to lose on this return."
Boss: did you make a sale?
Me: Yes
Boss: good job
Im sorry but if you work in sales and your boss gets upset at returns your boss is new to sales.
Seems pretty obvious to me that the job of the sales person is to make sales not talk people out of sales because the company is worried about returns.
We never worried about returns, if some one buys something they don't want we checked the recipt and checked for rocks in the box then just sold them something else, because you know sales?
The only reason I can think of a sales person being worried about returns is if a customer walks in asking for X and the sales person talks them into Y. Customer will be back fuming if it doesn't do X and you won't sell them anything else.
1) Apple is pretty well known for NOT up-selling and for right sizing customers, so you could actually get reprimanded at an Apple store if the sale was something as egregious as "gave customer laptop in smallest box".
2) The example we are talking about is a perfect setup for a "fuming customer"; smallest box laptop was "wrong laptop".
3) Apple depends on repeat sales and eco-system lock-in. The customer who returns the laptop may not upgrade their iPhone.
4) The request was ludicrous ... the Apple sales associate is not in the wrong for not simply going with it.
2) They got what they asked for I know customers get upset easily but there is no easier customer to handle than one that got exactly what they asked for.
3) They won't upgrade their iPhone? I thought apple didn't push that sort of thing? Anyway they are coming back in store to exchange you can easily make another sale there.
4) The request was simple, the apple sales associate is in the wrong for not helping the customer.
"I want the one in the smallest box for <reason>"
Instead of providing no reason and being smug in their assumption that they are both very clever and the barely over minimum wage employee assumes they are "stupid".
Also perplexing: footnote 2 mentions the car tire paradox. (Traction is determined by weight and coefficient of traction, and those two things only. So why do high performance cars have wider tires, which shouldn't make a difference? Because softer and stickier tires are mechanically weaker and tolerate heat less well, so you need to spread the force out over a larger area.) But it doesn't actually mention the answer besides noting many other people are wrong, and also is separately incorrect and says contact area doesn't change based on tire width?
Like, there's no clever counterintuitive Boyle's law/hydraulics effect where at the same air pressure a tire twice as big deforms half as much or whatever. Just the very obvious intuitive case that wider tires have bigger contact patches, which you can calculate yourself by plugging numbers into this tire calculator: http://bndtechsource.ucoz.com/index/tire_data_calculator/0-2... and the BMW i3 electric car has a crazy thin tire to have a smaller contact patch and less rolling resistance: https://www.bmwblog.com/2015/04/24/bmw-i3s-tires-more-import...
And the css thing... notoriously, everything on danluu.com has been completely unstyled for years. So every time one of his posts is on HN, someone comments about the unreadably wide lines, which could be fixed with a single `body{max-width:600px}` CSS rule.
But the reason everything is unstyled is because Dan installed octopress seven years ago, which had a braindead default theme that used custom fonts for everything, causing a glacial 15 second time to first paint: https://danluu.com/octopress-speedup/ Irritated, Dan ripped out all the CSS entirely, and the site loads in a flash. But now he has a trapped prior,[1] and any time someone says "CSS" to him he thinks, "ugh, that awful garbage which ruined my site" and refuses to touch it.
1: https://astralcodexten.substack.com/p/trapped-priors-as-a-ba...
Do you know that's true? Are you extrapolating his mental activity from a limited set of facts?
It is a bit condescending in my view to withhold that information from the clerk. But then again, I'm only making assumptions. Also, I've done similar things where I refused to let on my internal reasoning for various reasons. Sometimes just to mess with people. And clearly, many people thought me a fool for it. If I'd actually told them my reasoning? In many instances that would not have improved their opinion of me. So no loss.
There are also many instances where I could have benefited immensely from sharing my reasoning, because people could have corrected my mistaken assumptions. Can't say I've got it figured out when to keep shut and when to share.
At best he purposefully made things more difficult than they had to be. She was absolutely right to think that he was a "bozo." I generally strive to make things as easy and painless as possible for service workers I deal with, because I've been a service worker. It wouldn't surprise me if he has never spent a day in his adult life working a service job.
Regarding whether this actually happened or not: did any notice that "small box" item is one of the few he doesn't actually explain and he's withholding information from us just like he did from the salesperson? It feels like a "look at me, I'm so very smart, watch me manipulate my audience" move.
His disdain for his readers is pretty obvious from the fact that he puts zero effort into readability; there isn't an drop of formatting, it's just a massive wall of text from edge to edge of the browser window.
My assumption is that he really didn’t know which computer came in the smaller box (since, computer size, which is the public info about the product, doesn’t exactly correlate with the box size).
My guess is that he wanted to know which, if any, impact a small box would potentially have on computer components (like different impact absorption on transportation) that would require some CPU design adaptation. Like (speculation here, as I am nowhere near a CPU specialist): is a second memory clip more susceptible to be affected by transportation impact? So the box size is correlated with cheaper computers. Which tend to be larger computers, but can come in a smaller box because they don’t have that second memory clip?
Idk, but I am assuming good intent and reasoning behind the anecdote.
I still liked the article, I certainly have a problem with trying to avoid looking stupid too hard, at least in certain contexts.
Last time this happened, I needed steel wire, and I went to a guitar shop to buy guitar strings. I told the employee "this is going to be a bit weird but I want a string that is 0.3mm in diameter for a machine I'm building, do you have any?" instead of letting him be puzzled why I would want a "0.3mm string" rather than a "C string".
Usually people even ask and talk about about what I'm building, which is nice, but if it will take a long time to explain I say something like "it's not very easy to explain what it does because it's for a specialized purpose, but essentially it does <whatever general thing>".
I've never had anyone think I'm stupid, but not for lack of asking stupid questions, I think. I just take a little more care to spend two seconds explaining why I'm asking the thing.
You can see this as disdain, or as respect: I'm free to bring my own CSS to this page, and have things look exactly how I want them too.
He's like; fuck you for thinking the guy basing his $2000 computer purchase on cardboard is an idiot - I'm actually a secret genius CPU designer don't you know??
Well yeah like, maybe she's got a Master's degree in Packaging Design and knows that the smallest box, in fact, has weak cornering or cannot be reclosed because it has to be ripped open or something.
Is his request even well defined? There might be different, shortest, thinnest, shallowest boxes. Does it need to fit through a letterbox? Oh, ok, you don't care about depth then...
Not to mention the double meaning that "box" has in computing...
I noped out of the article at that point which is a shame because I do agree with the general idea.
Once I explained that, I was able to get what I wanted with no more questions. Now that they knew why I wanted what I wanted, they also knew what information was relevant to me. And I had already chosen the best model they had in that form factor.
Communication should be simple, direct, and complete. That's where I don't care if I "look stupid". I'll go over basics if there's a chance someone doesn't know the basics. Because you can say, "Oh I'm aware of X", but if you aren't and I assume you are, you may be too embarrassed to bring that up because you're afraid I think you're stupid if you don't know it.
Saying "It's a gift so I don't care about the model but it needs to fit in my carry-on bag" (or whatever the reason) would have explained it, and nobody would have thought the other was stupid. So in this case he's actively inviting that judgement.
Other than that, I also try to employ the naive question and to some people these might sound stupid. But they are really useful because they can clear up lots of implicit implications and misunderstandings.
Making any kind of judgments about their reaction to "I want the one that comes in the smallest box" is ludicrous; the behaviour itself is mildly sociopathic.
Good customer service is all about figuring out what people mean when they say ask for things. Sometimes they need genuine assistance, sometimes they just want to prove they are smart than you.
If one was truly not afraid to ask stupid questions, they would have humored the sales person. Just recently I got a discount on some laptop parts, entirely because I asked the sales guy questions about upgrading ram in a laptop I was buying, even though I already knew the answers, I just wanted someone to double check my assumption. So I asked if he could help me pick it out.
Turns out, he remembered that someone ordered, then cancelled the exact ram I was looking for, so he went to the upgrade center and got me a brand new stick of memory for the price of an "open box return."
Be nice to sales people, even if you build the things they are selling.
I agree with the general gist of the post: don't be afraid to ask stupid questions. However, the post has an underlying "feeling" of "my questions are not really stupid, I'm just so smart that others don't realise". I know that I ask plenty of stupid questions when I ask questions, I often realise how stupid they were just after the answer.
I scare people when im enthused about something. Its a bitch.
I know many people who would consider themselves non-technical, yet who certainly take the time to learn complex concepts. Some of those are indeed technological concepts.
> I try to give short simple examples because when I try to tell people the truth their eyes glaze over and their brain turns off while the nerd talks his techno jumble.
The short simple examples you give are also truthful, correct?
Perhaps the additional information you'd like to explain simply isn't needed for the other person's goal.
A great way to have both technical and non-technical people's eyes glaze over is detailing all kinds of minute details before describing some of the high-level goals or giving context as to why you're getting so deep into the details. As you mention, simple examples can get a lot across, and can be a springboard to more questions being asked, to allow the other person to decide what depth of knowledge they would like to know.
The non-technical person you're talking to may very well have the patience to learn the deep technical truth you'd like to explain, but they may have no reason to know it. In the scenario you're thinking of, you're doing the technical work, not them, correct? So why would they need to know deep technical details? A basic outline, with some corner cases pointed out, is likely all they need. Not because they don't have patience to learn what you're explaining, but because they have other things that are more important to their or your organization's success.
What a stupidly arrogant comment. Have you not heard of philosophy, for example?
Nicely said, I was trying to say that significant number of us is quite bad at it. And on the other hand, if frames are completely different, first compressed explanation looks like "noise noise word noise noise ...". On the other hand, often I see people struggling to start explaining as they know they will loose 30 min of time just to get to basics, so saying "I need computer in smallest box" - can be translated to "I want you to trust me and not bore me with you daily sale's pitch script you have learned by cart, I do not have time explain, I just need what I want not what you want to recommend me, unlike other customers I do not need your assistance I just need you to give me what I want. If customer is always right, just give me what I want, and I will make a purchase and you can move to the next customer."
Sometimes I think that this inpatient arose from search engines, where you type at most 3 words and you get your 10 results you were searching for. So, I assume it is reflected how we communicate with other fellow humans, demanding immediate results instead of 2 way communication.
We can argue it is rude, but for person who built his strong will over years in a hard way, attempt of manipulation and selling is also rude and intruding.
I do not have you ever been to Turkey or Greece where you have these shop owners who are literally trying to drag you in to the shop so you can buy something. For them it is like a ritual or the game, but if you do not want to be part of that theater show, you will find it very annoying.
In many Balkan countries they will ask you multiple times to eat or drink, and polite answer is "I cannot" but if you give that answer it is basically conversation starter for "Why? Are you ok? Is there something wrong...", it is part of social game to continue conversation. If you answer "I don't want to" although it is technically most correct, you will be showered with responses as "that is rude", "we will not poison you", "why is something wrong with my food", "why are you angry at me" ... and all you wanted to say is "I do not need any food or drink at this time as my body does not needed it, and I am perfectly content with my energy and liquid levels" :)
So, for many technical persons, who live most of their live in their own head, trying to juggle multiple ideas and resolve who knows what, small talk can be a major annoyance.
And I do not want to start with "this is secret project idea I am working on, I should not share it with anyone, someone may steal my idea ..." and everything along those lines...
> I eventually asked them to humor me and just bring out the boxes for the various laptop models so I could see the boxes, which they did, despite clearly thinking that my decision making process made no sense
Perhaps this is an unkind reading, but particularly the laptop scenario felt telling that this person might feel above explaining why they might prefer a laptop which comes in a smaller box.
On the surface that is very much a ridiculous request, regardless of how sensible it might actually be. Surely that shouldn't stop you from making the request, but you must understand that someone is merely doing their job to make sure that you understand what you're asking for.
If I go to a tuba shop and ask how many litres of ranch dressing it holds, I'm not going to scoff when the salesperson reminds me that it isn't a fancy brass bowl.
...come to think of it, maybe one of the grandmas was a CPU designer all a long!!
Sounds like this was the point of the blog post. He also drops that he was "very good" at Overwatch and "#1 in the world". Usually the people who want to tell others about this in public are not very good.
The ones who are very good are the ones who only tell you after you've tried teaching them. Since bad players in games often can't tell what good players look like, or how they play.
It's like saying "I know exactly which car I would like to drive every day because I designed the engine of a Ferrari".
No, but it heavily points to that you know basic things, like box-size != laptop size, or what CPUs do, and how to compare them, which is all the author claims.
I also found it striking how the post is emphasizing how important transparency in asking questions is which might or might not reveal the intelectual qualities of the person asking, but then failing to be that transparent towards both the clerk and the reader of the blog post about the internal thought process.
If one would like people to learn, enlighten them. :-)
That lack of transparency seems to be a theme. I have difficulty with blood draws as well and I have never encountered a health care professional that didn't immediately switch to "ok, which arm is usually best" mode.
In the end, every single one of the patients was correct. Anyone who typically had problems with blood draws knew their problems well.
Yes, most nurses listen. But there are enough out there that don't that I've seen it multiple times.
I've said nurses, but I don't actually know their professions.
Fair, it could just be my experience as a middle aged, white male coming into play here.
I ended up with hundreds of parking tickets, for all different makes and models of cars.
I quickly learned you get nowhere telling someone over the phone the ticket isn't yours because it's for a completely different make and model.
I simply asked questions.
What is the make and model on the ticket?
What is the make and model of my registered car?
Oh, they are different, why do you think that is?
Questions are sneaky.
I'm surprised I had to scroll this far to see someone suggesting this, since it seems extremely obvious to me that this is part of the case. It's becoming fairly well-documented that one of the primary differences in people on the spectrum is a difference in communication style, which anecdotally seems to be more direct and less apologetic or prone to "superfluous" verbal (/nonverbal) contextualizing.
With the prevalence of people on the spectrum in STEM, it's no surprise that you'd see it here, and indeed looking at the comments you can see quite a few people talking past each other about what OP "should" say with what is clearly a mismatch in communication style.
> I'm surprised I had to scroll this far to see someone suggesting this, since it seems extremely obvious to me that this is part of the case.
The whole thread has currently 1471 points and 681 comments. I seem the be the 4th person realising, that the whole discussion is about "communication advices given by someone fighting the spectrum disorder". I don't know wat to say.
1. Someone with a spectrum disorder.
2. Someone who enjoys dicking around with people.
3. Someone with a spectrum disorder who enjoys dicking around with people.
I'm trying to figure out if the person is in group 1 or 3. If you encounter a few people in Group 3, it's then harder to see people in Group 2 in a good light.
Even if this is wrong, I bet telling the salesperson that it was a gift and he wanted the smallest package would have avoided funny looks.
Acknowledging that you know your request is unusual makes it sound a lot less stupid.
Being willing to look stupid involves actually being able to deal with mistakes and failure, with actually _feeling_ stupid sometimes. Just listing a bunch of great decisions you made that other people thought were stupid seems less life-changing to me.
Maybe that's a subtle distinction, but I think it's important.
Have you noticed? We spend almost our entire adult lives doing things we’re good at. Anything we do that we’re bad at, we either stop doing or we get good at it. So all roads lead us away from the experience of being a beginner. For me, it had been too long. And I’d accidentally forgotten how to do it.
So I took up dancing (which I’m bad at). That was really terrifying. And trampolining. And more recently improv. At the moment I’m learning to draw - which I spent most of my life wanting to do. But I never stuck with it because I hate drawing badly. But that’s just what it feels like to be a beginner. The trick is letting that go, because it doesn’t matter. You don’t get to be good at anything without first being bad at it. And being comfortably, visibly bad at something gives everyone else permission to play.
I took up Jiu-Jitsu at age 40. Talk about humbling. I also catch myself occasionally doing what you did and mention how terrible I am/will be as a defensive mechanism.
But, the more comfortable I got at being a beginner led to even faster learning. This attitude has spread through other parts of my life, even areas where I'm not a beginner, and has led to improvement across the board.
I think there's a ton of wisdom in this. You learn to learn by, surprise surprise, being a beginner at something. Exposing yourself to broad areas in which you're a total newb can teach patience (I've yet to learn basic carpentry because I am one of those people who hasn't got the patience to measure twice), too.
This is really insightful: being a beginner is going to teach you how to learn things, and that's a hugely transferable skill. (Besides, it's also really enjoyable.)
"You are being nervous because you think that you might not be perfect, and doubt creates a feeling of nervousness and unsurety.
Well, I can dispel the doubt. You won't be perfect. In fact, you will be pretty lousy, because it is your first time, and it it is in front of a relatively large crowd.
So two pieces of good news. You needn't be nervous. And its not so bad that it will go lousy. Because everyone knows it is your first time, anyway, and they are expecting you to mess up. And this way, in the future, you will actually be great!"
A lot of wisdom there, IMHO
I have a 5 year old and a 2.5 year old, and hang out with lots of small children. Fear of looking stupid as a beginner is something that most people have right from the start: I have watched kids be afraid of incompetence (to the point of not wanting to try) at riding a bike, running, swinging across monkey bars, drawing, singing, reading, learning a new language, ...
Kids of 2–4 years old seem to have similar range of behaviors across substantially different cultural groups, e.g. comparing kids raised by tolerant non-confrontational hippies vs. strict immigrant professionals.
I imagine that learning to be comfortable as a beginner is something that can be trained / practiced. Some people certainly improve at it as they get older.
I'm a parent of a 5yo and surprised this is your experience. If anything, I'd say child behavior is the perfect anti-example of fear of trying new things.
Take one of the examples you provide: language. Young children ages don't care about using incorrect grammar or using the wrong words. This is why they're so good at progressing so quickly. Kids are way less afraid of failure than adults.
I also wouldn't be surprised if there's a significant environmental impact to children's behavior as well; in most ways, they're blank canvases when it comes to skill-based behavior. Personality...not so much.
The most important thing I have found when trying to teach kids [and probably most other people too] is (1) break tasks into very small steps, (2) make the lesson as low-pressure and fun as possible.
When you put the average adult learning a new language in a foreign country, they'll pause before new words, think before conjugating a verb, etc. Kids don't do that; they just talk. They don't worry about making a mistake, but adults (on average!) do.
The same kid will happily try riding a bike if you just leave one sitting around where they can find it, but will balk if you ask them to try in front of their friends who already know how. I think a huge part (the majority) of people’s fear of learning new skills is a kind of performance anxiety. Both fear of looking bad in front of others, and to some extent fear of looking bad to themselves. The other significant problem is an inability to break the new skill down into small enough pieces to manageably tackle independently.
Speaking a language is always and inevitably a performance. But kids are typically given much more time and space to just listen without trying to speak, and are judged less when they do try. Some kids who move to a new country will just quietly listen for months before ever trying to say something in the new language; adults rarely have that luxury.
But in any event, there are plenty of adults who are willing to try speaking foreign languages imperfectly, and studies have shown children and adults have comparable ability to learn a second language (indeed adults often improve faster at the start).
I don't even think they think I'm stupid, I'm sure they appreciate the fact that I've made every mistake before when they come to me for help later. I enjoy doing stuff more than I enjoy looking like an expert.
The blog doesn’t have an about me page as far as I can tell. Google says Dan is a systems engineer at Nvidia.
Edit: Found the About page https://danluu.com/about It's at the bottom of articles, but not accessible on the home page.
If this were an actual technical topic, I'd be more inclined to continue reading, but here, it's musings framed as a life lesson that could have come from anyone in my circle of friends. Life lessons from people whose only achievement is working at big tech. At least for my friends, they don't walk around assuming they're smarter than people.
The reoccurring theme in this post from Dan is he's not the one that's stupid, it's the people around him who are too stupid to see his underlying genius. Dan comes off insufferable.
I have another one. Why don't he spend 5 minutes making the content readable? Add some margins, it's all what it takes.
But Dan is on here because he generally writes well researched articles like [0] [1] and his minimal website aesthetics appeal to the HN crowd.
In this case, the post leans more heavily on personal anecdotes than survey data, so I can see why people are finding it a bit grating. And that mcguffin about laptop boxes isn't helping =)
I'm not sure why he's been posting more frequently lately. Usually I'd expect 1 a month.
Most people, if they rely on their own research and decision making, will do poorly. And even moderately clever people generally do better by copying the rare stray geniuses that float around in polite society. This manifests as an "unwillingness" to "look stupid". It is important to ask "what does stupid mean" and "how do I measure 'looking something'" when this sort of topic is bought up.
I am - and I don't think this is that unusual - willing to go about a decade ignoring the opinions of others if I'm really confident that I have an objectively good idea. It is a high-risk high-reward strategy and not for everyone.
Why is that?
That is a very subtle, fraught and complicated assessment. There is a lot going on to do with the audience, context, risk and the truth. There is a lot going on behind the term "looking stupid" and it undersells the complexity of the social interaction. There are two parties, multiple issues and a lot to think about.
So in general it may seem pretty noticeable, but in reality it's rarely so.
> In particular, it's often the case that there's a seemingly obvious but actually incorrect reason something is true, a slightly less obvious reason the thing seems untrue, and then a subtle and complex reason that the thing is actually true.
This is a good example of what's in the submission! It's "seemingly obvious" that people are judging you all the time, and slightly less obvious that people aren't actually thinking about you nearly as often as you think, but the few who are thinking about you might be indeed judging you to look stupid for asking "basic" questions.
That's an interesting assertion. I would have guessed the opposite is true.
People are hilariously bad at induction, deduction, and making decisions based on their own research.
We're biased because we're already on the internet, on this site, and nothing is on fire in our vicinity.
This is such an odd example. Because OP makes an uncommon request, the sales person can't parse what this request is about, and neither can I for that matter, and OP doesn't give a reason.
So the sales person thinks: What an odd request, which in turn is parsed by the OP as sales person thinks I'm stupid for asking something that the sales person doesn't understand. In the end, OP might want to feel superior by asking stupid-looking questions on purpose and feeling above the sales person for not being able to get to why this question is asked.
Maybe just explain WHY you ask this or that and nobody thinks you're stupid anymore.
Taking OP's thesis about the origin of "stupid questions" at face value, this small meta lift seems fitting.
Why did OP not tell the store clerk why a small box mattered?
Why did OP not tell the reader why he didn't tell the clerk?
We don’t but we think we might learn something or be entertained. Withholding a piece of information that lots of readers are naturally curious about is odd. I like the post & Dan Luu’s writing in general but I’m dying to know the why behind the computer in the smallest box request.
Because most average users ask for one thing, but actually need something else and it is the job of a service person to get down to what the customer actually wants. Disclosing intent of unusual requests helps to find a solution in a faster way. It's also respectful to the clerk. Furthermore, people are more willing to cooperate if they know a reason.
> why would the reader need to know that?
Because it stands out as an odd story and it is quite important to establish context if the reader wants to evaluate if OP asks objectively stupid questions, has a way of phrasing questions in a stupid way, or if the person asked truly thinks OP is stupid.
That's what this post is about with a strong tendency that OP wants the reader to think that everybody judging him is stupid. In a way, the post is a humble-brag.
> Do you need a justification for buying something from a store?
No, but if I make people run around for me, I'd rather give them a reason.
> I think that's the lesson here. If you think he needed to give justification, you may still consider him stupid in a way.
I don't think he's stupid, but I think if someone is being judged as stupid all the time, it might not always be the other people (what OP makes us want to believe), but the way how OP interacts with his environment.
> Because most average users ask for one thing, but actually need something else and it is the job of a service person to get down to what the customer actually wants. Disclosing intent of unusual requests helps to find a solution in a faster way. It's also respectful to the clerk. Furthermore, people are more willing to cooperate if they know a reason.
Which is hilarious because as software developers, we run into this all the time. People who request things or ask how to do things and it turns out what they needed was something else entirely.
Why wouldn't this apply to other areas.
As I said elsewhere, I think it's an instance of the XY problem and we agree here, but I think the response of the clerk could have been something like "I have a lot of clients that ask for X when they need Y. If I give them X, they may come back and complain, and it will be a mistake on my part. So I'm sorry if I'm being too insistent with it, but I really need to be sure that you want X and not Y, especially since your request sounds a lot like what people say when they want Y", to which you could reply "Oh I perfectly understand, I work in software and we have this all the time with clients, I would do the same thing in your place. I assure you, I really need X and not Y." or something.
> It's also respectful to the clerk.
It may be more respectful than what happened the way the thing was narrated, but I think there is nothing "respectful" about disclosing information you may not want to disclose, which seem to be the case here (or the author is being obtuse).
> That's what this post is about with a strong tendency that OP wants the reader to think that everybody judging him is stupid.
I don't agree about the intentions of the author here. My interpretation is that he found something cool, efficient, somewhat counterintuive and want to share it. That seems to be in line with his other posts.
> I don't think he's stupid, but I think if someone is being judged as stupid all the time, it might not always be the other people (what OP makes us want to believe), but the way how OP interacts with his environment.
That's very true too. We only have his version so that's a possibility.
Maybe there's additional context we're missing.
Author was just trying to be clever at the expense of retail employees.
Generally trying to be clever is ordinary life is not a good idea.
And was the encounter really antagonistic? Dan Luu is the one who left looking stupid.
Dan was asking the employee to expend considerable additional effort to find the smallest laptop box when he potentially knew the model number, or least had a reason that would justify the extra work. I would have just said "I'm really tight on carry-on space", not to avoid looking stupid, but to assure the employee I wasn't breaking their balls for no reason.
He touches on this later in the article after comparing thoughts to another person (who is block quoted) who seems to wonder the same things as a lot of commenters here...
The point is that this is a two way transaction with a real person, who has their own hidden state, goals and limits that are not always apparent to a consumer.
E.g. company policy on deducing what the customer really needs.
How was the employee to know Dan was the one person who actually knew what they needed, out of 100 over confident buffoon's that came to the shop that week.
This is why I don't hassle the support person fixing my internet when they run through support script.
I don't say "skip this, I have an honours degree blah blah", cause they have enough constraints to deal with as is... And once in a 100 times, I will learn something I didn't know...
Anyways, if you tell a store person "oh, I'm getting this for my husband" when it's a gift for yourself, that's more honesty than dishonesty, because to the store person, "clarity" with a customer is very goal oriented. Dan Luu wasn't trying to screw with the store person, and in the end they all got what they wanted, even if Dan Luu walked away "looking stupid".
That he doesn't care if he looks stupid is besides the point here. He looked stupid to the retail worker not because he didn't explain his underlying reasons for wanting a small box. He looked stupid because he didn't understand the retail sales process. That is to say, he was stupid, about that one thing, and that is why he looked stupid.
The question is really what kind of person do you want to be? Do you want a person who habitually lies about unimportant stuff in order to accomplish goals? Do you want to be a person who is genuine but gets unfairly judged by strangers? Or do you want to be a person who justifies themselves to strangers in order to avoid getting judged?
If you think lying is wrong and seeking the approval of strangers is a bad habit only one option remains.
I guess the reality is that huge majority of customers in those shops aren't proficient at technology at all,
so it's incredibly good bet that customer has no idea what s/he's doing.
Part of the job of someone working in a customer-facing, sales job is to understand what the customer wants. A sales associate at an Apple Store probably has dozens of interactions every day where they're able to help people understand the products better and enable them to make a more informed decision. That is their job.
Saying "I just want the one that's in the smallest box" makes you look like a customer that's in need of guidance and help, and someone who's probably going to have a bad experience with the product if they don't get it.
Getting irritated by a response that is trying to help just shows a lack of empathy. People are not robots and there is a really good reason that the "white lie" is a thing.
Not only that, but he is also implying that people "who design processors" must also know our way around shopping for computers. This couldn't be farther from the truth.
So this story does not come off as an example of "I don't mind being seen as stupid", it comes off as a very strong example of "I'm holier than you"-attitude which is the entire opposite than the article author's is trying to make.
Exactly my thoughts.
Even the way the story is told to the reader with: "which I had a good reason to want at the time", has the same sentiment towards us.
"My reasoning is even above explaining to you, my reader."
Extrapolating from this article, this individual is likely a nightmare to work with due to their closed nature and unwillingness to share thoughts or decision making points.
> I try to be careful to avoid this failure mode when onboarding interns and junior folks and have generally been sucessful, but it's taken me up to six weeks to convince people that it's ok for them to ask questions
I kind of get the impression that asking the author questions is actually a very painful process.
Probably not.
People are shallow and often don't spend a lot of time trying to understand other people.
You won't always have the luxury to explain yourself.
---
But he lost me with the examples of the Apple computer box. Employees aren't little robots- they're actual humans that (mostly) are trying to be helpful. It would've taken Dan -significantly- less time and effort to just say WHY he was looking for a smaller box. Probably the same deal with the auto insurance agent- he could've just explained WHY he wanted such an unusual request, and the agent likely wouldn't have incredulously asked him 3 times.
In my experience people are straightforward and respectful with you when you're straightforward and respectful with them. Waltzing in and going "give me the thing in the smallest box" makes absolutely zero sense and it's like Dan was just purposefully playing a game of being obtuse towards random help staff... People aren't intelligent or stupid because they get confused when someone comes in with very unusual requests that they refuse to elaborate on.
---
Also, I truly don't get the box thing. Technology-wise it makes no sense. Why doesn't Dan explain the reason in this post either?
—-
Last edit: I had an unusual situation once in Seoul at this one cafe that I visited a lot. There were two registers, and for some reason my credit card just wouldn’t work on the left register. So a few times I just asked “Hey, this is an unusual request, but could we use the machine on the right? My card works on that one, but not this one.” And guess what? The employees went “oh, ok” or “sure”.
It took slightly more effort on my part than saying “hey, use the machine on the right”. But then nobody was confused. It had nothing to do with the employees being intelligent or stupid or being perceived as such.
The first few paragraphs are meandering and, seemingly, deliberately obtuse. Many of the examples are examples of a kind of "I'm so much smarter than you, I can play the stupid" arrogance that is incredibly off putting in real life because it leads to a bunch of bad faith questions and interactions.
I really get the impression that the author is an unreliable narrator and that they are always the hero of their story. It is pretty easy to read many of the examples as the person NOT thinking the author was stupid, but rather that the author was a arrogant, condescending ass (especially the Apple store employee, their insurance brokers and every medical professional they have seen).
Turns out he was the top student in the program and I would guess this was due in part to his willingness to ask questions and lack of fear in asking them in front of a room. He helped me get through an Operating Systems course the next semester.
More importantly, he showed a young me that asking questions is actually a sign of maturity and intellectual honesty and that what the peanut gallery thinks is of little consequence. That lesson has served me well in the last decade. He's now a PhD at a major research university and a close friend.
To be honest, this entire post make him look stupid, but we all know now that he doesn't care what we think. I'm probably stupid for falling for another one of his clever schemes where he's just pretending to be stupid.
This isn't just looking stupid, this is being stupid. Why in Heaven's name wouldn't you at least adjust your behavior when you're in an interview?
Acting stupid can be a convenient way to hold up your belief that you're smarter than the rest. Nobody will ever challenge your belief because hey, if they think you are stupid, it's because you made them believe that, which means that they are actually the stupid ones!
They saw my weird resume - it always gets a comment. It was revised and edited under direction from a retired entrepreneur and CEO who explained how employee employer and employee/employer/HR/hiring managers interactions work "in real life".
They did a phone interview. They called me in. The only times I get the "thanks for interviewing, but" calls is when the recruiter or headhunter obfuscated the job description to prevent poaching and/or losing their commission/bonus and I had literally no idea about any of their stack/business/whatever.
I could just be lucky, I guess, not having to lie or embellish or present a facade.
If you care about what people think of you, perhaps you should first ask if there's anything you can change instead of expecting more from others.
Except for this part:
The person who helped me, despite being very polite, also clearly thought I was a bozo and kept explaining things like "the size of the box and the size of the computer aren't the same". Of course I knew that, but I didn't want to say something like "I design CPUs. I understand the difference between the size of the box the computer comes and in the size of the computer and I know it's very unusual to care about the size of the box, but I really want the one that comes in the smallest box". Just saying the last bit without establishing any kind of authority didn't convince the person
In that case I most certainly would have established that I knew what I was talking about, and also explained exactly why I cared about the box. Maybe the author never worked in retail or public facing tech support, but when you're in those jobs you learn to not believe anything the user/customer says. At least until they let you know they know what they're talking about.
The asking questions part also reminded me of a story from when I was a junior network engineer in my mid 20s, working with two guys in their 50s who had each been doing the job for over 15 years. A little bit after I started they gave me a task that required me to use a system they knew I didn't have access to. After about an hour I figured out that I would need it. I asked them how to use the xyz server, and they both started laughing. It was a test to see if I would ask for help. Apparently the last guy who had to do that task waited 3 days before asking for help, and didn't even figure out he needed to use the system in question. They decided to see how I would handle it, instead of just telling me outright.
Get jacked and all these problems disappear. No matter how silly your questions and objections, no matter how dumb they may think you are, all your concerns will be treated very seriously, criticism couched in most polite terms, and weird stuff written off as eccentric.
(It helps to be taller, well-dressed, and sound sophisticated but solid deadlift is by far the most effective.)
It's not the mark of an "incel" to take note and think this is important.
I noticed a marked difference in how I was treated and respected when I gained weight. When I was skinny, I was pushed around and ignored.
When I gained weight, suddenly people were wary of me and much more likely to accept my input or requirements.
I didn't even exercise. I merely gained weight.
Software engineers and computer scientists like to think they're above this stuff, but they aren't.
If anything, I think the meathead/jock/gymrat stereotype is more pervasive.
And sure they might think you’re a meathead, but they sure won’t tell you that.
In all seriousness though, this comment almost sounds like its from another language when read here on HN. Its crazy how completely wierd some parts of the internet has become.
The judgmental people tend not to matter in the long run, by the way.
Sort of. There are two types of judgmental people. One, the people building a team, or making a bet. Two, the people looking to talk about others.
The latter don't matter. The former are quick to judge because they have to be. If they're wrong about their bets, it'll soon become obvious. Which means the optimal strategy is to make many bets, or to interview as many devs as possible, and then cull most of the candidates.
It's not personal. http://www.paulgraham.com/judgement.html helped me care way less about rejection, which seems to decrease the odds of getting rejected.
(I reached for your profile to email you the "nice username" thing, but there wasn't any way.)
At the time, I was young, insecure, and fraught with imposter syndrome (viewing virtually everyone as smarter than me) so I took it personally. That feedback gave me a visceral "that has got to be the worst feedback ever" reaction.
Fast forward 10 years, I've reached the point where I don't think twice about asking questions in any setting. I'm secure and confident in what I know, understand the vastness of what I don't know, and try to be vulnerable about this truth. I'm no longer worried about looking dumb. Maybe some people still think "well that's a dumb question, he should know that" but I'd rather have this experience, while retaining my adaptability "superpower" of being able to dig to the root of a problem, quickly learn context, and rapidly provide solutions.
I think about that feedback a lot.
===
They gave him an intelligence test. The first question on the math part had to do with boats on a river: Port Smith is 100 miles upstream of Port Jones. The river flows at 5 miles per hour. The boat goes through water at 10 miles per hour. How long does it take to go from Port Smith to Port Jones? How long to come back?
Lawrence immediately saw that it was a trick question. You would have to be some kind of idiot to make the facile assumption that the current would add or subtract 5 miles per hour to or from the speed of the boat. Clearly, 5 miles per hour was nothing more than the average speed. The current would be faster in the middle of the river and slower at the banks. More complicated variations could be expected at bends in the river. Basically it was a question of hydrodynamics, which could be tackled using certain well-known systems of differential equations. Lawrence dove into the problem, rapidly (or so he thought) covering both sides of ten sheets of paper with calculations. Along the way, he realized that one of his assumptions, in combination with the simplified Navier Stokes equations, had led him into an exploration of a particularly interesting family of partial differential equations. Before he knew it, he had proved a new theorem. If that didn’t prove his intelligence, what would?
Then the time bell rang and the papers were collected. Lawrence managed to hang onto his scratch paper. He took it back to his dorm, typed it up, and mailed it to one of the more approachable math professors at Princeton, who promptly arranged for it to be published in a Parisian mathematics journal.
Lawrence received two free, freshly printed copies of the journal a few months later, in San Diego, California, during mail call on board a large ship called the U.S.S. Nevada. The ship had a band, and the Navy had given Lawrence the job of playing the glockenspiel in it, because their testing procedures had proven that he was not intelligent enough to do anything else.
[0] It's possible he gave an answer that wasn't what they expected and it was "incorrect".
As in, the reasoning applied to some of those cases is quite Vulcanian-like, maybe a comrade on-the-spectrum?
1. You start by asking the "obvious" questions, the things everyone is supposed to already know. Question every assumption, every bit of "common sense".
2. Along the way, you discover that most people don't truly know what they claim to know. Instead, it's just years of built-up bias.
3. Soon you're asking questions no one thought of asking in the first place.
4. Finally, you understand the subject better than anyone, because you started by questions the foundational assumptions and built up from there. You see how all the pieces connect. (To my fellow programmers: This is, I think, why many of us dislike frameworks... too many levels of abstraction from the real thing.)
Related concepts:
- Always be willing to be the dumbest person in the room. It means you've surrounded yourself with people smarter than you, so you can learn from them. It also means they'll help you be far more successful than you could on your own.
- Don't try to outsmart everyone. Just try to avoid dumb mistakes. While everyone else is trying to impress each other with their brilliance, you can calmly do the next right thing, and avoid the next dumb thing. Charlie Munger credits the success of Berkshire Hathaway to this principle more than any other. It means being willing to LOOK stupid in order to avoid actually BEING stupid.
My own experience has been that if you’re pretty sure you’re one of the smartest people in the room, you have an obligation to ask the “stupid” questions, because the rest of the room will be too afraid to look stupid.
I really agree with that but it's all about being willing to take a risk.
Many settings, especially in corporate environments, are intrinsically hostile to inquiry. These are places where meetings are run with semi-parliamentary rules-- just pro-forma affairs to mark project transitions.
In such situations, it may be that the others know better than you do and thus STFU or else be silently, immediately, and permanently dismissed for future consideration by those who call the shots.
Recently, I've been learning to sing better, with a focus on my higher register. One of the reasons most people cannot sing high notes well is that you inevitably have to go though a phase of singing high notes badly (and very loudly) first. Being a 'bad singer' (especially thanks to TV talent shows) is often seen as a paragon of looking like a dumb, shameful, naive idiot who overestimates their ability and lacks talent. This is despite the fact that every good singer was once a bad one.
I've noticed this same pattern in varying degrees of extremity across many sills I've picked up over the years. It is when you are in the 'stupid' phase, regardless of what is is you are learning, you're unlikely to get any sympathy positive reinforcement from the world, before then hitting an inflection point where you get loads. Knowing that you need to push through this to succeed is golden.
Fundamentally I work as a consultant. It's my job to solve other people's problems, which we usually (but not always) do by building something for them. Often our clients deal with a lot of consultants of different forms - they use consultants because they have specific skills and knowledge in different areas. Unfortunately this means that everyone is always trying to sounds as smart as possible and never admits to not knowing something. For the client they then don't know if they're getting "this is something that I know from doing 100 times" from "I'd guess this is the answer".
I've found that answering the occasional question with "I don't know (but I'll find out and get back to you)" changes people's opinion of me (and my company) for the positive. They suddenly (usually subconsciously) have greater trust of what we're telling them, because they know we'd admit if we didn't know.
Those are not examples of asking stupid questions. Those are examples of asking good questions in a stupid way, almost like he is trying to look stupid, for no good reason. Why don't you give your interlocutor some context so they can help you better? Is your goal to instead make them look stupid? I truly don't understand.
and that is to act stupid/ daft - not just one question, but for periods of time. and see how they respond to you
a very effective technique when dealing or interacting with so called Subject Matter Experts. If they're an expert they should be able to explain complex stuff at a High/ medium/ low levels or just say they do not know.
If they're not really an expert then they cover up their lack of knowledge
I fell in love with HN because of the quality of the discussion which was rooted in a sincere attitude of "There are no stupid questions" (assuming you were asking in good faith and not trolling or sea lioning or something like that).
And I'm not enjoying HN as much as I used to and I think part of it is I love asking the "stupid" questions and getting real answers from knowledgeable people and I feel like that's much harder to find than it used to be.
When I was a respected Principal Engineer, secure in my position, I was willing to look stupid.
When I was in a contract-to-hire position, where I had spent months looking for a job and where I was constantly judged and I thought I might be let go at any moment, I was not willing to look stupid.
When I was a long-time group leader and project architect, I was willing to look stupid.
When I worked at a place where I was in the political and religious minority, I was not willing to look stupid.
One shouldn't be afraid to look stupid in situations where that fear is groundless. But I think it's worth having some empathy for people who are in a situation where looking stupid could actually be a threat.
It's true that I often care way too much about looking stupid and this post is really useful for reexamining that mindset and seeing how it's a mistake. Setting my ego aside and doing the best action regardless of how it makes me look would benefit me 99% of the time. BUT, I've had people in charge of some thing I care about dismiss my thoughts or contributions because it appears to them that it's not worth their time to pay attention to me. If I am collaborating on something that I know or care a lot about, I want my questions answered well and I want my contributions taken seriously. Sometimes that means I need to go out of my way to get the respect of this person. Being professional, making efforts to let someone know WHY I am asking a question, and asking revealing questions that benefit others' understanding, are not always a waste of time.
But maybe we should educate our society so that this isn't the case anymore? I know this sounds unattainable, but we should still try to make such outcomes invalid.
P.S. I guess the article does touch on this when it mentions the anecdote about the people in class and the "dumb" questions being posed to the teacher. Come to think of it, I guess the whole article is kinda like a commentary on this phenomenon actually :).
I believe the author thought the clerk was too stupid to understand the real reason and it would be a waste of time to explain to the clerk why.
I remember the first time I heard the statement: The only stupid question is the question you don't ask. This statement bewildered me, because I thought I might be the one that asked "that" question. If this sounds confusing, I most likely read that statement as "the only stupid question is the the one you shouldn't ask and if you don't know what makes a question stupid, you're probably too stupid to know."
This fear of asking stupid questions made me unwilling to take math courses beyond Geometry. I ended up getting further math education when I started my IT career in 1990. I overcame my fear of asking questions in the course of doing my student teaching assignment before that.
Donald Rumsfeld was both actively intelligent and very actively stupid. Staying away from him was smart.
He could have just asked the Apple droid to bring out one of each laptop in its box, and picked one without saying why he was picking that one. The whole transaction would have gone quicker. So, making himself look stupid produced a predictably suboptimal result in that case.
When I turned 40 about 10+x years ago, I started wearing garish colors and weird jewelry, and styling my hair differently every few months. I'm talking mullets, or perms, with yellow blazers, leather bracers with gems, purple pants, rings on all fingers, red shoes, bright green shirts with zebra stripes... I rotate everything routinely.
Now people expect I'm going to say weird things and look at me suspiciously.
Random people start friendly conversations, local people I see when I walk to the store tell me the look forward to seeing me.
It's called not giving a fuck and it feels fantastic...
The best part was how condescending he would be when you asked him to explain himself. You could tell he thought you were a dope because you couldn't follow him because in his head he was a genius.
I wonder how many times he thought he knew better and it bite him in the arse? He did allude to it, but I suspect it far more often than he would be willing to admit.
> Car insurance: the last time I bought car insurance, I had to confirm three times that I only wanted coverage for damage I do to others with no coverage for damage to my own vehicle if I'm at fault. The insurance agent was unable to refrain from looking at me like I'm an idiot and was more incredulous each time they asked if I was really sure
This is typically more expensive as people that get third party insurance are usually newer (and younger drivers) so the insurance company will charge you more because their algorithm for determining cost will factor that in. So I don't doubt he was getting strange looks because it likely cost him more money and you don't get the obvious benefit of full comprehensive.
This and the laptop situation screams of "I made a strange request and didn't explain my motivations and then I wondered why I got strange looks".
It is just him communication poorly. Which isn't anything to brag about.
> On the flip side, the person I was living with at the time didn't want to wear the mask I got her since she found it too embarrassing to wear a mask when no one else was and become one of the early bay area covid cases, which gave her a case of long covid that floored her for months
The whole mask effectiveness isn't as straight forward as he thinks it is. His flatmate after the mixed messaging from the media probably thought it was a wash and decided to just fit in with everyone else and was unlucky as a result.
I have no idea why this guy is so popular. Whenever I read anything from him he seems completely unlikeable.
EDIT: Rephrasing.
Well, okay, but maybe the non-stupid thing is to not move to a wildfire risk area.
In general the list of circumstances where the author was willing to "look stupid" to strangers because he was, in fact, clever and seeing into the future, is mildly irritating.
Feynman's first wife put it better: "what do you care what other people think?"
An American asking a Brit "Do you know XYZ?" The foreigner will reply "A little" and to an American that means the know nothing - an American who knows "a little" will say they are good at it.
Partially, because in IT -- seemingly more than in other industries -- variations of the phrase "Why haven't you just ..." arise, "just" being that magical simplifier which compacts all complexity into a single and obvious step, and often come with some measure of "why haven't the boffin pressed the button, I told the boffin that the button needs to be pressed" attitude, and I do not want to do that to someone else.
The other portion of it is being the rubber duck, quack quack.
I think that's a case where the Apple store employees err on the side of caution. I would bet that they have more clients asking for the smallest box while wanting the smallest computer compared to clients asking for the smallest box while needing the smallest box. I think that's an instance of the XY problem https://xyproblem.info/, and people being trained to recognise it and having a false positive.
> Air filtration: I did a bit of looking into the impact of air quality on health and bought air filters for my apartment in 2012
To take the "opposite view" (as in, don't be afraid of talking to people who look stupid) from this, I love talking to people about these kind of things (if they are willing to talk about them, of course). In many circumstances, I learned a lot by being charitable, open and ready to hear the thoughts of someone about something, even when they're unconventional/look stupid. I think I have that position because I deal more with "look stupid but are smart"-type people, while the Apple employee store or the stackoverflow user seem to deal more with the "look stupid so I have to protect them from themselves"-type people.
But I cannot help but compare this to negotiation. It is a lot easier when you negotiate from a place of abundance. Negotiating salary is easier when you do not need the job. Negotiating a house is easier when you do not need to buy that house.
I feel like the same applies here. Willingness to look stupid is a lot easier in situations where you have confidence and nothing to lose.
Nothing says ego in the backseat like an iamsosmart blog post. Bonus points if the website looks like it's from 2005 and if you write it in a tone as if you just invented penicillin.
The examples the author gives are more about being indexed on what others can't see than him being ignorant - but "stupid" is an interesting one because that means something else. If you separate intelligence and smart as being a capactity for abstraction and clarity vs. being able to get or achieve the things you want, one person can easily be both hyperintelligent and completely un-smart. Nerd is the cliche for that. The low cunning of a middle manager can produce outcomes that are very smart, without much talent for complexity, discovery, truth, or consideration, which is reflected in other archetypes.
I often admit I'm not particularly smart, and that mostly I'm stupid in such unexpected ways that people conclude I must know something they don't, because nobody with a rudimentary apprehension of reality would attempt the things I have. Beware an idiot with the element of surprise. This is to say, I look stupid every day, and it is often painful and has a permanent record, but I see it more like lifting weights, where given the options, using your body to shift hundreds of pounds without leverage is definitely short term stupid, but the effects of persisting are long term smart.
I realized this when trying to learn Salsa dancing. Some people have a natural talent, but most don't and that includes me. It was one of the most difficult things for me to learn and it took months of very very bad dancing to get to a passable level.
As a guy, it can be tough post-college to make other good male friends, but I look back at all my male friends now and they are almost all from Salsa. There's a real camaraderie that comes from passing through a challenge together and making it to the other side.
Sure - it's not a Navy Seal experience or something that intense, but the fear of social humiliation is a strong one and if you can get through that with some other solid people, it builds a real bond.
Full quote from Gervais Principle here: https://dustingetz.com/d4337a942961484b8b408d4b1963e161
My transition from developer to founder is marked by needing to win more (all) transactions with minimized variance. As Warren Buffet says "never lose money", you might think it's +EV to apply Kelly Criterion here and risk a bit to maximize alpha, but in soft human affairs there are too many unknown unknowns to quantify risk, you need to keep it simple and not lose transactions. IMO
I'm very much like the author, in that I just ask questions and don't worry about looking stupid (what a silly thing to worry about), but I think my friend is the polar opposite, and this article really helped me understand the dynamic between the 2 of us a little bit better. I always wondered why he would get super defensive if I correct him on anything, but it makes sense if he thinks I'm stupid and is getting corrected by the stupid guy lol
I can't say it's news: I'm like that myself. It has it's downsides though. I focus so much on the real world, things like spending hours on personal grooming to impress others just don't happen. My wife thinks I'm a slob. I'm a very tidy & clean slob, but it's true.
I'd imagine that it's not so viable in more aggressive/competitive/toxic environments though? But I've been lucky avoiding those.
Edit: Oh and sometimes my questions do turn out to be ... a bit dim. Most recent case that springs to mind was asking the local equivalent of "what does SSN stand for?" in a context where I really should have known. But the average outcome is good.
When I was younger I found out that things that were hard for me were making me angry. I would say that "this thing is stupid" or "it sucks". Where in reality I was stupid and I sucked.
At some point I realized it was that I simply don't understand something that made me angry and then I started using that emotion as a telltale that I should step back and learn a bit more about the thing.
In the end it evolved that I don't get angry anymore at things. I directly realize that I don't understand something and accept that I have more work to do on understanding it.
and particularly
> it's very important that you know that they think that you're stupid and will keep increasing the intensity of their responses until you acknowledge that they think you're stupid.
I rarely get criticised or mocked and I think it's because I'm tall, white, and male. If I say something naive, people are almost always accommodating (ok, not on the Internet) because they don't want to risk offending the big beardy dude.
This is a shame because I've spent much of my life:
a) thinking people are basically kind and accommodating b) not being questioned, so missing a potentially valuable source of data with which to check myself and improve
Not minding if you might sound stupid comes from a place of security in your life. If you already have a solid in-group, then the fear of being rejected by some other group starts to go away and you feel more comfortable risking looking dumb in front of people.
I think it comes from a deep instinct to find allies and show that you’ll be a valuable member of a group, or at least not a liability.
When picking up my kid at kindergarten once, I got an urge to jump over the fence into the yard, rather than using the gate. Of course, a 49-year old doing that might look stupid to all the kids and staff present (lots), so I did it. Then a 20-year old staff member comes up to me and says “Yeah…so we try to teach the kids here not to climb the fence. It’d be great if you didn’t do what you just did..”
Sometimes looking stupid means being stupid too. But that’s ok.
I applaud your fence-jumping! I think children learning that it's ok to have fun as an adult is a much more important (and rare) lesson than learning that sometimes you have to abide by arbitrary rules
The sight of a young child holding the bars wistfully looking out at the inaccessible world beyond them is just painful.
Not that a moat or geofenced electroshock collars would be better.
I suppose "rubber duck debugging" is a form of this.
Sounds kinda dumb, but it was an ah-ha realization that extended beyond finding misplaced items.
Like "Willingness ..." it's a tool to remove your ego from and look-for/work-with 'talent' thru a (slightly more) objective lens.
As an individual contributor, it opens you to alternative ideas (learning from others). As a manager, it allows your team to build confidence and be open with you about problems and potentially radical alternatives.
A variation on this idea: + the only things I know I learned from other folks.
4k screens can easily support ridiculously small font sizes, but you wouldn't decide to use that just because it's there. Similarly, you would not want 15 inches long lines of text completely breaking the concept of paragraphs just because your screen can reach that width.
For individuals that service is largely inseparable from risk transfer, i.e., you can really only get it through insurance. Lawyers can handle a subset of the process, but not all of it, and besides, relying on lawyers for it is probably at least as expensive as the non-risk-transfer component of insurance in expectation.
In general, if someone's wealthy enough that they can effectively self-insure, even if they're completely risk-neutral, their time is probably valuable enough that they'd be better off buying insurance just to avoid having to go through the equivalent of the claims process themselves. So unless the author's rationale is wildly different than I'm thinking, in that example his insurance agent was right and he did make a stupid decision.
In nicer cases, they get so amazed of how well you play the piano when in reality they're one of the greatest of pianists and you're just a beginner.
It's difficult to tell who is who. Knowing this, I cautiously assume everyone is smart. Sometimes, it's scary how smart/skilled someone actually turns out to be.
Being in that 'good stupid' state makes you initially acutely uncomfortable (once the decision sinks in), but later on it proves to be not so stupid, in fact the best thing you could have done. 'Ignorance is bliss' may be related. Lots of 'stupid' simple minded people have come out well in life.
But often times stupid is real stupid and lands you in trouble - we all know that side of the equation - now maybe even that has a reward to it - in terms of the lesson learnt.
In 7th grade, a teacher upset me for some reason I can't even remember. But being a brat, I went through this phase where I decided to waste her time and constantly pepper her with just tons and tons of questions about what we were learning. Some just "stupid" questions I already could surmise but wanted her to have to frustratingly retread over. And some legitimate things too where I just wanted her to go deeper into something.
I would love to apologize to that teacher of course. I was definitely being a spiteful jerk.
But incidentally, I noticed my grades were getting better.
It dawned on me: the more time I spent coming up with questions, even ones that students would groan over how stupid they were, the better I'd do. Admittedly some of my questions probably didn't even need to be asked, but I decided to stop filtering myself on what's a good question. If there was any doubt at all in my head, from something a teacher would say, my hand would shoot up.
And so I just kept doing that through high school and college and noticed when I was vigilent at this, my grades were great. I think some of this behavior has stuck with me, maybe not perfectly though. I think getting older and being seen as an "expert" in some fields now, has probably biased me to stop asking as many questions unfortunately. But ruminating on this experience and the OPs is a great reminder of that bias, and maybe something I can keep improving in myself.
Just be like this girl :P
https://www.youtube.com/watch?v=7q89tdSjE-0
>Learning a sport or video game: I try things out to understand what happens when you do them, which often results in other people thinking that I'm a complete idiot when the thing is looks stupid, but being willing to look stupid helps me improve relatively quickly
Overall author came up with this concept of "looks stupid", yet it does already exist as "failure teaches more" or just "curiosity" in my opinion.
Overall2:
Maybe
Why Is It So Hard to Be Rational?
https://www.newyorker.com/magazine/2021/08/23/why-is-it-so-h...
His ability to explain the complexities of Pascal, Basic and eventually C++ totally changed my life. I never became an amazing programmer, but I was a hacker at a time when that was valuable and it completely changed the trajectory of my life.
He set the bar for simplification of a subject and edification of an individual. It's something I look for and at some understanding someone's ability to explain something became the primary way for me to assess their intelligence.
The best way to do that? Ask really stupid questions.
That has really really worked against my in some contexts. I spent a lot of time working for a large US company and while many of the smartest and most capable executives LOVED those conversations where would explore the outer bounds of their new ideas, many of the mid level mangers truly thought I was a f$#ing idiot. They could not get past their impression of my after one simple, stupid, question.
I still don't know how many people I have left in my wake who truly think I am dim. I don't really care, but it took me a lot of years to realize how it was perceived.
People at that company didn't know me well, yet, and as I said, I wasn't core to many of the meetings I attended, and I spent most of the meeting sitting quietly with my eyes closed. Never assume I am sleeping. And don't try to wave off my 'stupid' questions. I ask the stupid questions, because if you cannot address it with a simple direct answer, then you don't understand the stupid question.
The way I push myself in front of the stupid bus is by intentionally putting myself into situations where I cannot possibly provide a 100% smooth delivery. For example, instead of spending an hour to refresh myself on a complex code question before hopping on a 1:1 screenshare (presumably so I can look like a total smartass), I will ask the other teammember to fire up a screenshare right away without any planning. The consequence is that I inevitably look a little lost every time and the other team member has to remind me of the gaps as we go through the problem.
Over time, I believe this builds a strong sense that even the lead/architect is not better than anyone else and that we all have an ongoing role in keeping each other synchronized on the relevant domain knowledge.
What's much more self-destructive than being afraid of looking stupid is feeling like you need to look like you know 100% of what is going on at all times- this inevitably leads to bullshitting and half-truths and weird circuitous conversations where it's unclear who actually knows what. Never try to conceal ignorance. People who matter and people who you actually would want to work with and work for would never judge someone for admitting ignorance or asking questions. People who don't matter, and people no one would want to work with or for are the ones who get on someone's case for asking what they think is a stupid question.
During my master, one of the students laughed out loud after I asked a question during class. I told him "there are no stupid questions" and he replied "your question was stupid though". Guess who ended up with the better job.
In my previous job some guy berated me publicly (on slack) for asking too many questions.
I try to be careful to avoid this failure mode when onboarding interns and junior folks and have generally been sucessful, but it's taken me up to six weeks to convince people that it's ok for them to ask questions and, until that happens, I have to constantly ask them how things are going to make sure they're not stuck. That works fine if someone is my intern, but I can observe that many intern and new hire mentors do not do this and that often results in a bad outcome for all parties
In almost every case, the person had at least interned at other companies, but they hadn't learned that it was ok to ask questions. P.S. if you're a junior engineer at a place where it's not ok to ask questions, you should look for another job if circumstances permit
If you want dependable, competent people to work with, you need to give them the space to become those kinds of colleagues.Over on another danluu post thread about productivity, I kept asking why it was assumed that one had to maximize productivity and go fast as a prerequisite for having leisure time. But no matter how I asked why it was asserted that leisure is dependent on productivity and why relaxing is predicated on first clearing some bar of an acceptable amount of work, nobody really wanted to examine that. It was just taken as a given. One response even shut down further discussion with "this isn't a philosophical discussion".
So it seems to me that it's really only considered ok to ask stupid questions and look stupid within a framework of what's acceptably 'stupid'. But probing into the underlying assumptions themselves is not an acceptable kind of stupid.
Which leads to my stupid question: who determines, and how, what the acceptable limits of "stupid" are? And how are those norms communicated and enforced?
It’s a lot easier when you are established in a career/network/relationship and have erected a safe space around yourself. You can unmuzzle your inner confusion without threat to your status or ego, as you know you’re not really stupid.
Not so easy as an outsider, or as a junior where you secretly worry that you might be stupid.
Maybe he means another metric, e.g. by volume? But:
- first problem, he seems to expect that people with whom he talks should not make assumptions
- second problem, does he really expect the store clerk to calculate the volumes of all the boxes?
I don't know, are we sure he is not actually stupid?
I think the car insurance example is perhaps an example of the three-part explanation talked about in the article because sometimes comprehensive cover is cheaper than third party cover (the argument goes 1. Comprehensive is better because it covers everything, 2. Third party is cheaper because it covers less, 3. Actually comprehensive is sometimes cheaper for weird reasons like riskier drivers self-selecting for third party cover) but I could also be wrong here. An obvious way would be that the author’s case is not one where comprehensive cover is cheaper and a less obvious way would be if comprehensive cover is deceptively cheap (eg maybe if you get into an accident where the insurer covers first-party damage because you have a comprehensive policy, your future premiums under any policy are higher than if your insurer had only paid for third party damage.)
Back in college, there was one group of folks that, for whatever reason, stood out to me as people who really didn't understand the class material. When they talked, they said things that didn't make any sense, they were struggling in the classes and barely passing, etc. I don't remember any direct interactions but, one day, a friend of mine who also knew them remarked to me, "did you know [that group] thinks you're really dumb?". I found that really delightful and asked why. It turned out the reason was that I asked really stupid sounding questions.
And that group of people, when they failed tests or scored badly, it was always the test that was "unfair".
I wanted to write a blog post about this very topic for a long time, but it has now become obsolete because there's no way I could do a better job than Dan. Outstanding.
The one step forward is willing to be stupid. That is you know you are stupid but still not try to hide it. And most of the time it'll just be that: you are stupid. But once in a while you discover something deep.
When my ability to actually implement functionality was incommensurate with their perception of my level of understanding, they would still privilege their perception as colored by me asking very basic questions (which despite appearances can often yield surprisingly useful/surprising information).
Despite being aware of what was 'going on', and generally having high confidence, this still impacts my self perception on some level. I find when I optimize for being perceived as intelligent instead of actually trying to understand things effectively I get much better reviews. It's difficult to know which is appropriate if you want to advance your career.
There's a difference between not saying anything and asking "What are you referring to right now specifically?", "What does DMA mean in the context of the server?" and "Sorry, I'm very experienced with X. How hard would you say is it to do Y with it compared to doing it with Z, which I have worked with in the past?".
Not only does it show that a person is listening, but it also improves the ability of everyone in the team to express and elaborate on details that are relevant to the topic being discussed.
https://geraldmweinberg.com/Site/Exploring_Requirements.html
One time we were learning about volcanoes. And, of course, that they erupt. I was thinking about how the eruption is dangerous and causes harm, and what we could do to prevent it. My first thought was, well, to put a cap on the volcano. So I raised my hand and asked the teacher "what if we put a cap on it?", and everyone laughed.
Another time we were learning about plants, and how if you give them too much water they will die. That immediately sounded insane to me and I raised my hand to ask, "Wait, why don't they just not drink it?!"
Both of these stories lingered around for years and people knew me as someone who lacks "common sense" and who is known for asking silly questions.
Many look at a problem as a frustating situation, and wish it would go away.
That's what "they think I'm stupid" is mostly about.
Most people just want things to work, which is understandable and reasonable, but not rational. It's wishful thinking, that has no action or teeth.
In reality, constant change and development will always bring about frustration.
The true problem is accepting that you can't control everything.
But after realizing that, pretend that you are in control.
Be ok with the results, no matter what's the ultimate solution.
ie. Ignore what you can't control, and BE YOURSELF.
BUT, listen to your elders.
Listen for at least 3 months. Think about it. If you're still willing to listen to their advice, but don't want to take it, go slowly forward, and live your life.
The next generation is always unfathomable to their parents, but you need to respect, and listen, for they truly do know things you don't know, but the reverse is true as well.
If you ask dumb questions, the person speaking (if they’re any good) will start looking to you to figure out if they’re pitching their language correctly. The other people in the room who didn’t understand will be relieved and quietly thankful of you because they didn’t have to be the ones to ask. And people who understood already are usually way more chill about this sort of thing than you would expect. Especially if you give them the opportunity to explain something in front of everyone. And then thank them for doing so.
I don’t think I fully understand why, but asking dumb questions is often a subtle act of leadership.
Very much so. It helps establishing an environment with less ego, more helpful people, and people who aren't afraid to learn. It also diminishes feelings of imposter syndrome in other people, by showing that not everyone knows everything.
All of those are things leaders should incentivize.
The only way to get power and money is to have people with power and money want to give it to you. For that to happen, you have to share a majority of thought process, opinion, etc.
This generalises well... ultimately if being pretentious is valued over being genuine then it's probably not a valuable or healthy place for you to be, situation to be in, or person to be around.
For the other more common example of the intern/junior who fears looking stupid to their own detriment. Their only defence is that work places exist which _do_ actually prosecute people for asking "stupid" but useful questions - if they happen to be at such a workplace, it's not worth staying anyway.
I noticed in classes that people were afraid to ask questions, and when they did, everyone else was happy they did so since we all had the same question in mind, usually. So at some point I decided I'm just going to ask any question that pops into my head and stop caring what others think.
It worked out great, but now that I'm married, it annoys my wife to no end, especially with an engineer mindset. Like the old joke "go to the store and get milk, if there are eggs, get a dozen", and the husband brings home a dozen milks. I ask these seemingly subtle, stupid, clarifying questions all the time (ie: "a dozen eggs, right?"), and it makes my wife angry -- still after 10 years of marriage.
Earlier in our marriage, she would make a vague request or statement as a prompt for me to do something. Instead of asking for clarification, I would do what I _guessed_ she wanted. And I would often get it wrong and be met with the response of, "You knew what I meant!" No, clearly I didn't, or I wouldn't have done the wrong thing.
These days she is getting better at being clearer about her needs and I am (maybe?) getting more diligent about asking for clarification.
This seems fine, but I've found a better approach in this sort of situation is to—as much as possible!—explain your reason to the person helping you. It's not about seeming less stupid (although that is one of the outcomes) but about giving the other person room to help you with your actual goal. When somebody understands why you need the smallest box, they'll have no reservations about finding it for you, and they might have even better suggestions you didn't consider (eg "order this laptop online, the boxes they use for shipping are more efficient").
And that's very often to great advantage when you're trying to discover something about a system that people would rather not reveal.
[1]: A lot of our arguments boiled down to us debating stuff where neither of us knew what we were talking about, but I was the only one willing to admit that.
For example for some bizzare reason I am percieved as strange bu very inteligent and yet when I ask the questions they are rarely percieved stupid.
Why I am not going out of my own way to sound smart or anything I display depth of knowledge at certain areas and the way I'm asking questions is in an honest inquisitive matter of fact way.
The other side of this is the way one perceives the reactions, for example they might not reacted as if one was stupid as much as they are confused at disparity between the question asked and the knowledge one has showcased before that question.
Meaning, we know that some things cannot be understood until they are tried, and trying such things often leads to failure (though there's an art to keep the failure small and learn fast.)
So we'd basically recognize and reward people for embracing that reality, for the ability to say "yup I am gonna probably do this wrong the first time but that's gonna lead to progress"
Inverse of that is fear of failure - inability to do something unless you are certain you're capable of securing a successful outcome. Basically that means you only do things you already know how to do.
I am starting to recognize that the courage is required because it can be a filter. It isn't just the chance that a "nurse or phlebotomist" might judge you harshly, there are many people in the world that'll sooner reject than connect with you.
Still, if we are to be true to ourselves, perhaps vulnerability can minimize the total amount of pain in our lives. It'll take weighting the acute pain of rejection as vulnerable as lesser than the chronic pain of acceptance with insecurity.
May we be so fortunate to choose.
Nobody knows everything, and even if you're a hyper-conformist who always tows the line and parrots experts instead of evaluating ideas from first principles, you ought to find peace in the fact that 500 years from now (and perhaps even some in our lifetimes), people will look back at many of our most fundamental, passionate, and obviously true opinions with a mix of disdain, pity, and fascination.
The opposite also happens. You ask a stupid question, and people try to give you "smart" answers that aren't actually answering your first question, because they assume you're stupid / "doing it wrong".
A lot of the international students, especially from Asian countries, would never ask such 'stupid' questions for fear of losing face. This became apparent for a lot of them in the final presentations when they still didn't understand the real problems
It's remarkable how many of the "stupid questions" ends up sounding like the synonymous "reviewer 1". And how many end up catching out high level problems which are lost in the detail in something new and exiting. Such as "OK we build and install it there and calibrate it, but what about networking and power in year 2 after the upgrade?"...
I think there’s some stuff here where he could have done a better job explaining why he was curious about something (the smaller computer box).
Generally people are afraid to ask questions when they’re afraid to look stupid. This creates a harmful feedback loop.
Part of the reason for this fear is cultural.
I try to go out of my way to encourage new hires to push through this fear: https://zalberico.com/essay/2017/02/21/asking-questions.html
One of the hardest lessons to learn in life is to not concern yourself with what others think of them.
Be polite, courteous, and caring because you want people to like you and you don't want to be ostracized but those things come from within.
But, "I want them to think I'm successful/hot/smart/cool/etc" is just a good way to show how you're not any of those things. So many stories are about people who try really hard to maintain these personas and they all fall apart from the tension.
Delightful anecdotes in this article. Well done.
We should be confident enough that we stand by comments even if we expect some of them to be misunderstood/unpopular. There are always people who will agree and always some who will agree. Once we can judge ourselves fairly, we won't care what other people think - we can be judged by our outcomes.
"You don't need more control over everything, you need more courage". In a lot of ways that dovetails with Dan's comments.
You look stulid and are stupid.
You look stupid but aren't.
You look smart but aren't.
You look smart and are smart, but people think you're just virtue signaling. But you know that virture signaling actually saves you time discussing why your aren't stupid while still looking so.
etc. pp.
In my opinion, real gain in looking stupid is when you actually are and then know how to accept valid critique, or at least try to understand where it comes from before you know it's valid.
Because then you actually learn something that could improve your situation.
The other day I got confused by a decimal separator on Hacker News and posted a comment saying so. I am pretty sure some people assumed I was stupid. Perhaps they did not want to put in the effort required to understand why some one might get confused in the given situation.
I will admit sometimes I fall into this trap too and assume the other person is stupid. Nobody is perfect.
I have nothing profound to say, just wanted to share this.
When you try to post low-level questions on a high-level forum (no matter what trade it is), you will get negative responses, because you dilute the topic. It's like having speed bump in fast lane.
But some of the items are more about presenting information in a way that makes people change their actions without feeling stupid.
Like the ones about blood draws. I've seen my wife do this so well, and I honestly never knew it was possible to live so harmoniously with society. People are just so much more helpful and flexible with her and I attributed it to her Dale Carnegie levels of persuasiveness.
Maybe it's not the same thing, masks and air filters have more obvious benefits than avoiding accounts at restaurants.
I think this post might be triggering a lot of people who feel it might be criticizing them. It takes a lot of emotional energy to _look_ stupid in front of people, in ways that I would guess most people here (including myself) don't.
But I believe that it’s also very cultural and gendered so it’s not as easy or successful for everyone, unfortunately. (Adding) I mean not easy personality wise due o their background, OR not easy because people more often treat them as stupid given an excuse because of who they are or what they look like.
Another helpful thing would have been examples. What were the stupid questions he was asking in college?
These are good points in the article; two other areas I'm willing to look stupid are:
- asking a store employee where to find specific items (quicker than most men)
- communicating in simple (almost childlike), direct rhetoric. As I get into more intellectual circles, I've found that my reputation does take a hit, but I still think the mental throughput/accuracy of expressing ideas simply is worth the reputational hit
This trait is shared among almost all of the mathematicians I've respected deeply and it's always astounding how the most trivial lines of questioning can lead to deep, profound realizations.
I spent some years at a FAANG, some of them in management, and it was shocking how many meetings could be unlocked by one person willing to risk sounding stupid.
I was also shocked by how many people would approach me after to say they were wondering the same things.
The flip side to this, was that I would also occasionally step on someone's favorite baby, which they usually didn't like much.
It's one of the things I felt got better when going from high school to university - in high school I felt like I needed to do both to get good grades (because of how much of your grade came from the teacher's impression of you) whereas in uni, I didn't have to bother and could just focus on learning.
Unwillingness to adapt to circumstances maybe isn't stupidity, but it's definitely self-limiting.
It would be fun to have a list of these ideas. Anyone have any examples beyond the footnote in the article? (why wider tires have better grip)
For adults, looking smart is more important and if asking dumb questions hinders that capability, then we tend to avoid it.
Great read!
*Complementary to the headline and premise, at least; a bit less so the actual contents.
The secret is that we're all dumb as bricks - most of us just dont act like it, and so they go on being a brick. Those of us who are self aware and unashamed can be slightly less stupid on a good day. That's about all we can hope for, but it's worth it imo.
(I'm talking about experts with/for whom I've worked, to be clear, not myself.)
When you say it around people who are generally quick witted, it takes a second for them to grok what you're saying and then they figure out that you're cracking a joke and then they smile, usually laugh.
But years ago I found myself working as an aircraft mechanic. And my cohorts whom I rode around with were very blue collar in language and culture, and several of them had been chosen as "mechanic" because they hadn't performed that well on an aptitude test.
So one day I made one of my famous observe-the-obvious funny statements, and one member of the group whom I'm pretty sure was one of the low aptitude scorers, looked at me with obvious disgust and said, "You must be one of the dumbest people I've ever met."
He didn't understand why I started howling with laughter.
Idiots.
This seems like a really long example of a typical narcissistic interview answer to "what is your biggest weakness?", of "people think I look stupid but actually I'm really really smart".
It's amazing to me how conservative people are with their mental energy. Many people hate to think. Not because they can't! Just because they would rather not. I'm not sure why.
You can train yourself to invoke it when the feeling comes up, if you didn’t have the chance to preload it before the interaction.
I think the only requirement for it to work though is that the intentions behind your questions are whole.
Asking childish "why?" questions is often very illuminating, although if it causes you to stumble into some aspect of incompetent leadership then be warned.
Most of the time it lowers expectations people have of me and relieves me from the worries about not being able to meet said expectations.
I never stopped doing it. I will never stop. I do not care. At the end, what I want, is to know new stuff.
I never considered that this might be common. I guess I shouldn’t take myself as an example.
You can actually make this a habit and it becomes hard to fix!
If you ever want to start a company, you have to make it a habit to look impressive.
I've found that the less I give a damn about what other people think at all, the more enjoyable life is.
The thing is; if you have no authority, you have no responsibility; and I'm clearly not in control of other people's thoughts.
If you don't care how you're perceived, that's fine. However, you'll be missing out on many opportunities because reputation matters.
The other half is ensuring that certain things get into the official judicial record.
My standard classroom experience is that I ask “dumb” questions all the time, often eliciting guffaws.
By the end of the class, though, everyone is asking me for help (even the guffaw people).
For me, really understanding the material is critical. I can’t deal with rote.
I think that's why many comedians are extraordinarily smart. Not because comedy requires intellugence, but because it requires looking stupid.
If one does that, they are part of the problem. Please leave other people alone. You do not know anything about their personal situation.
This post could be called "Unwillingness to appear human"
Reminds me of Nassim Nicholas Taleb and his practice of being obviously arrogant to assholes.
But.. why tho?
If you are wealthy enough (and mentally prepared) to absorb tail events without much negative effect on your life, it can be perfectly rational to not insure damage to your car.
body {
max-width: 80ch;
margin: auto;
}BTW what's wrong with this? Honest question!
In the context of the article, I imagine it's that some Kubernetes expert couldn't design and sell them an overcomplicated microservices-based solution which would basically only really be useful at Netflix-scale.
I think this is remarkable, how common people with some level of scientific literacy were able to get this correct much better than the whole medical establishment.
I don't think it's remarkable at all. Common people with some level of scientific literacy took basically all kind of stances about masks. Some of them had to be right in the end.
'The medical establishment' otoh had to come to one single common recommendation and as it's only one there's a chance of failure (there were, ofc. individual medical professional and scientists who got it right as well).
And they have to be able to communicate it in an effective way such that people believe it... AND can act on it. AND can act on it in a way that doesn't trigger panic or totally mess with supply chains needed to get proper equipment to front-line responders.
like Lawrence from azangru's quote above, the medical establishment needs to consider many more factors than 'common people' before making a public statement.
Further, my former co-workers from my stint in HIV testing were ALL saying wear masks and don't count on a vaccine being available until 2021 at the very earliest. They all started self isolating very early.
The whole "medical establishment" DID know this.
This was a failure of leadership of the medical establishment to either listen to the rest of the medical establishment or to effectively push back on the political leadership.
Sure, that might very well be what you aim for, but from my understanding, FFP2 should prevent both, at least theoretically, since wearing them correctly is another point of failure.
Agree. This could be a post in itself.
https://journals.biologists.com/jcs/article/121/11/1771/3003...
― Confucius
There is way to much of this bullshit all over the place (e.g. PPE use) and I'm quick to judge people who do it, because I find it a truly moronic attitude.
Well, if I think too much, probably I think more than you about your own profession, so, I do not want to say this, but you are not the best possible professional, because sometimes I had the feeling that she just follows the trend instead of getting genuine opinions about some of the topics in the discipline.
I can't remember his exact words, but my takeaway was not to be afraid of asking super basic questions.
(Also, it probably doesn't need to be said on HN again, but that really is a good book.)
Your ideas would then spread more.
"Dare to be Stupid" - Weird Al Yankowich https://www.youtube.com/watch?v=SMhwddNQSWQ
Asking questions is really putting print statements(or functions) in ordinary, physical world. It's debugging yourself or your surroundings.
Asking questions is crucial when you're doing sports and trying to improve your personal best - for example pull ups or squats. Eventually a joint or tissue starts to hurt and you need to figure out why or you get an injury. Am I doing it too often? No warmup? Bad diet? Sleep? Does your joint rotate too much and in which axis?
And you will absolutely not get far in a puzzle game like Baba Is You if you're not good at asking questions. When I got stuck in that game, it was almost always due to a wrong assumption I made early on and failed to recognize. Solving the game is similar to tree traversal. If one approach doesn't work, and you don't have another idea, you need to re-examine your assumptions.
1. It is usually combinatorially impossible to answer all the questions when solving a problem - people just choose some random walk over the problem space and it doesn't always lead to ideal results.
2. It is socially unacceptable for "senior" people (who usually have better mental model of higher level concerns) not to project smug confidence in front of less "senior" people, so they pretend to know things they do not.
3. People have evolved to be lazy as fuck, so unless they absolutely must know something and can't do without it, they mostly won't even bother. Some won't bother even _if_ they can't do without.
I don't have solutions to #1 and #3, and I doubt #3 can even be solved at all. But I do have a solution for #2 - it's the Socratic method (or as they call it at Microsoft "precision questioning"). It lets you save face by asking pointed, outcome-oriented questions of someone who likely knows more about the problem, without necessarily making your own lack of knowledge obvious. Besides that it also surfaces the assumptions, some of which routinely turn out to be wrong, and it's the easiest method I know for getting people to change their mind on things, because they feel like they've arrived at the answers using "their own" thought process. It is difficult to master, so it too runs into #3, however, but I think all engineers, senior and junior would benefit from learning this. Another upside of learning it is it makes it harder for unscrupulous others to manipulate you maliciously via Socratic questioning, since you know what they're trying to do.
I sometime find myself deliberately avoiding looking stupid because it could possibly damage my career. And that's because the people who make decisions are not some divine being who see through you, they are just humans like the rest of us.
But still… it can be taken too far. Just as a matter of being a person who can socialize normally, what’s wrong with spending a few seconds explaining yourself? “This is gonna sound silly, but I want the computer in the smallest box. Here’s why.” That kind of thing.
I don’t let my ego get in the way of learning new things. But I don’t go out of my way to sound like an eccentric weirdo either.
I mean, stupid people do exactly the same stuff. The difference is their thought process is actually flawed but they're confident they're right.
The only difference is in being objectively right or wrong - either way, just be confident.
Smarter people seem to have trouble with that because they are often open to learning/being corrected and second guess their decisions.
> For example, if a date thinks I'm stupid because I ask them what a word means, so much so that they show it in their facial expression and/or tone of voice, I think it's pretty unlikely that we're compatible, so I view finding that out sooner rather than later as upside and not downside.