[The_Colonel]

I think you're missing the point, this is not about the split between management and engineering. Code monkey is here somebody who accepts assignment and produces code, without having a lot of understanding for the larger whole.

And that's mostly what you get with this attitude that doesn't value any meetings / communication which doesn't relate directly to one's work.

But the organizations don't want to have code monkeys (typically), because to produce value, people can't just churn out code to complete assignments, they need to also understand the context, be able to identify made up problems, be able to design the most minimal solution covering the business needs etc. That requires understanding, certain alignment, communication.

[giantg2]

They might say that they don't want code monkeys, but their actions say otherwise. That's my experience anyways.

[JohnFen]

I don't see anyone arguing that communication isn't a critical part of working.

> And that's mostly what you get with this attitude that doesn't value any meetings / communication which doesn't relate directly to one's work.

But all the things you've listed in the following paragraph are totally communications that relate directly to one's work. What is the case that unrelated communications are also essential?