[Joeri]

Focused work is essential to quality results in programming. I guarantee you that whatever piece of software you hold most dear as an example of how software should be made, the key parts of it were written in long uninterrupted stretches of work. Thinking up good solutions similarly is a focused work activity, and meetings are almost entirely unsuited to thinking of great solutions that cover all the edge cases (although they can be ok for thinking of good enough solutions).

Now, to understand the problem to be solved, to agree on a solution being proposed (out of the results of focused work), and to synchronize the progress when multiple people are working on said solution, this does require communication, and meetings are often a good way to do this. They are therefore essential to enabling the long uninterrupted stretches of work to produce great outcomes, but they must not come at the expense of that focused work.