[t43562]

So far most of the objections to the article are about how being wrong has consequences. That is of course the reason why you MUST not fear being wrong:

When a group of people are setting out to achieve something and succeed they must be able to do it close enough to right that it serves its purpose. This means they all need to do work that comes together into a correct and harmonious result. They cannot make something harmonious if they have different understandings of what they're doing and it cannot be correct if they have failed to foresee some important aspect of the problem/solution.

So you talk about the problem and your solution and explain your understandings and that allows the other people to correct you or possibly to see something they hadn't seen.

This is where you risk being wrong and MUST do it so that before you start taking actions you can be corrected. If you hide your misunderstandings then there will be consequences.

We peer review code and nobody likes being criticised but in the end it when it saves you from being the one to introduce a bad bug you tend to be grateful. Similarly with ideas - you put them out for review.

A work environment where you cannot safely put your ideas or code out for review is a toxic one and likely is wasting a lot of its potential.