Modern testing for modern stacks

We will all face this issue in our careers. Its good to know about this bias as it helps us to avoid doing this mistake. When we speak to people from other domain we experience it more like when we speak to a developer he kind of assumes we know something about the code and functions. One way for us to fight is asking questions - feeling ok to say I didn't get you or I don't know the background. When you are the conveying any message try to be clear, give examples. It's always better to over-communicate.

This is a very good article.I like it very much. When I was reading this article,I can remember much about my previous working experience. I have come across with many people they are technically good and but they donot know how to deliver it to the audience. This what we call it as curse of knowledge. First step is make sure to whom we are going to deliver the presentation on that our presentation should be prepared. Then the next step is move forward slowly about the topic. Give the higher level introduction for the topic and then go deeper to the subject. Next step What I can say here is try to give more stories and examples related to the subject so that audience will get an idea of what we are going to deliver it. The final step is show our presentation to someone else and get the feedback from them.

This is a good read. This bias exists and am glad that its been written.The example of teacher and student is so true.I could relate to several situations.I could think of my daughter learning new words and I teaching her.I need to put myself into her place to teach better.Also, I could relate to the situation at work where we see this bias evidently.Many people feel embarassed that they dont have the knowledge compared to the others. Though the bias exists, I think no one should hesitate to say that they dont know.

The curse of knowledge is not only about knowing things that other person does not know but you are too far away from the situation of being a learner. So it is harder to put yourself in the shoes of someone who's not familiar with that thing. You cannot go back to that point and no longer remember what difficulties you had when you were in the learning phase. When we suffer from the curse of knowledge, we are like the tappers, just because we know the melody of the song that we're tapping to we assume that others will know it too. But often, the other person 'the listener' doesn't have the same information as we do. To overcome curse of knowlegde, we should be able to communicate in a way that is easy for people to understand. Knowing your audience is absolutely key and talking in a language that your audience understands and using concrete examples, taking feedback from people are some simple techniques.

The curse of knowledge can be a barrier when communicating to/within a team. With respect to testing we will find this in action in two places,1. When we update the team with our status on a particular job,2. Communication to the developer about a bug. I liked the https://hbr.org/2006/12/the-curse-of-knowledge;at/1 article that Summet shared. I agree that using phrases like 'Achieving customer delight' can mean many things to employees when communicated by an executive. The employees are out of context hence every one would have their own idea of achieving the end result.

It's a good wiki page, explaining keyword curse of knowledge. It's basically when you know things that the other person does not and you have forgotten what itΓÇÖs like to not have this knowledge. This makes it harder for you to identify with the other personΓÇÖs situation and explain things in a manner that is easily understandable to someone who is a novice. One example I can give from my past career is that When you are an engineer you try to explain any issue giving the technical aspect of it also but the person who is listening to you may not have an idea about tech he may be a support staff or sales guy. One more experience was when I joined Browntape the CTO over there gave us a good overview of Web architecture and other stuff and he could do so because he was knowing what problems he faced when he was also a Fresher.

Curse of knowledge sounds like a hollywood movie name to me :) If we are deeply into something , we under communicate and expect how could others miss what we said is the result of curse of knowledge . I think every one of us face it many times in our day to day lifes .How do we avoid curse of knowledge atleast in important situations of our day to day lifes , I think one way of doing it is to over communicate is better than under communicate and other way is to be prepared and can try it out on someone before getting into real important instances