As an engineer, I'd rather be called stupid than stay silent
1–10 of 15 posts
Re: As an engineer, I'd rather be called stupid than stay silent
#2"The man who asks a question is a fool for a minute, the man who does not ask is a fool for life".
Plus, I like to tell my team: a stupid idea can be the seed of a good one.
Re: As an engineer, I'd rather be called stupid than stay silent
#3stupid questions are the most important ones - they mean something very deep is missing / misty / doubtful / wrong. Smart ones are usually on the surface.. "assuming" the depth is okay.
https://journals.biologists.com/jcs/article/121/11/1771/3003...
Re: As an engineer, I'd rather be called stupid than stay silent
#4stupid questions are the most important ones - they mean something very deep is missing / misty / doubtful / wrong. Smart ones are usually on the surface.. "assuming" the depth is okay. https://journals.biologists.com/jcs/article/121/11/1771/3003...
As someone who has been censured for recommending the word "imbecility" to describe a healthful state of mind that we should all embrace:
I think a HN-friendly way to reword such advice is:
Don't shy away from poking at your own confusion, because sometimes you get to poke others as a bonusRe: As an engineer, I'd rather be called stupid than stay silent
#5See also "The Stupidity Manifesto"
https://insimpleterms.blog/the-stupidity-manifesto
"LET’S STOP MAKING EACH OTHER FEEL STUPID. Instead, let’s encourage everyone to ask questions"
Re: As an engineer, I'd rather be called stupid than stay silent
#6stupid questions are the most important ones - they mean something very deep is missing / misty / doubtful / wrong. Smart ones are usually on the surface.. "assuming" the depth is okay. https://journals.biologists.com/jcs/article/121/11/1771/3003...
Sure but there are also stupid questions that waste the groups time. They are common in university lectures.
Some people, like maybe 2%, seem to have a urge that when the lecturer asks for questions, someone has to ask one to not make the lecturer sad.
Re: As an engineer, I'd rather be called stupid than stay silent
#7Yes, but it requires a truly disciplined management layer to foster such an environment, e.g. not commenting negatively in 1:1s on the comments of a 3rd party and remediate immediately any such accidental remarks that might hurt the safety to be vulnerable.
Re: As an engineer, I'd rather be called stupid than stay silent
#8Great advice. I think it's one good rule. It needs to be combined with other good rules, like "meeting time can be precious".
Re: As an engineer, I'd rather be called stupid than stay silent
#9The opposite of this, actively over explaining, is also a great way to grow trust and your career. By trying to anticipate questions when communicating at work, or writing code, you open up the room for others to ask questions and speed up finding solutions especially in situations like in the article.
Re: As an engineer, I'd rather be called stupid than stay silent
#10The opposite of this, actively over explaining, is also a great way to grow trust and your career. By trying to anticipate questions when communicating at work, or writing code, you open up the room for others to ask questions and speed up finding solutions especially in situations like in the article.
Overexplaining things you don't have a good grasp on is not the best idea idea out there. Asking questions can help piecing together some understanding which when when communicated and has some kind of feedback, does have a good effect on further learning. I used the word communicated instead of overexplaining which I find a bit overbearing. Overexplaining... If the point gets across the first time why repeat it ad nauseum?