LOL. Unfortunately what people say that you can hear can affect your team because of product interactions. And people tend to talk about other things than work. Additionally, they are often wrong which requires correction.
> Unfortunately what people say that you can hear can affect your team because of product interactions.
Absolutely. However that is a lot less common than things that you hear that don't affect you. If you want everyone to know everything than you can't have more than 10 developers - a team of this size (or slightly smaller) will be far more productive than larger teams because they know all the interactions - but the larger team because of the larger numbers gets more done at the end of the day anyway (and good architecture will minimize the interactions and thus help productivity)
> Unfortunately what people say that you can hear can affect your team because of product interactions.
When it is only a small number of people those non-work conversations make your teammates more human and thus gel your team and so are worth thee cost. However if the number of people is too large it is a distraction.
> they are often wrong which requires correction.
If they are your teammates you should be correcting each other. If they are not - you shouldn't be the expert in the subject and so you won't know they are wrong in the first place.
