I think that this article raises from the wrong experience with Meetings, more exactly the wrong focus.

Developers do not speak because most of those meetings are not really oriented to the job that they do, instead, they are more focused on what the Scrum Master or any other role is expecting. Given that the objective of the meeting is getting the approval of such roles, developers do not feel free to use these meetings effectively (and the aren't allowed either).

More funny is that I addressed this same problem with a very different solution, and frankly, more effective one, in one of my latest articles:

- https://drpicox.medium.com/agile-retrospectives-for-rigid-people-9e94fba6beb3

TL;DR Developers do not speak, not because they are shy, nor because they are antisocial, but because they cannot discuss actual work.

I have present in meetings in which developers can actually work, and I can say without any doubt that those very productive meetings are very boring for scrum masters and other roles. And, once retros are well focused, developers ask for them!