It's an argument for having meetings when you need them, with whoever you need them with, with no particular schedule or routine attached.
> I care quite a lot what the people in my team are working on.
Do you really? Or do you just want to signal that?
> Otherwise why are we even a team?
You are on a team because that's the unit of organization above the individual.
> It's the opposite: if developers are not communicating, they're probably not cooperating with each other, which means something is very wrong.
If developers need to cooperate, you have a problem that you should avoid at great cost. Of course, sometimes cooperation is unavoidable, but it's not a good thing in and of itself. Don't let anyone tell you otherwise. Aim to split up your work to require minimal cooperation. This may sound like unconventional advice, but anyone with enough experience managing developers will likely agree.
> "To a first approximation, nobody cares what you're working on. Nobody should care what you're working on."
I care quite a lot what the people in my team are working on. Otherwise why are we even a team?
If you're not in a team, obviously things are different.
> "If your developers need to constantly communicate with each other, something is likely very wrong with the way you split up your work."
It's the opposite: if developers are not communicating, they're probably not cooperating with each other, which means something is very wrong.