Add to that the fact that the meeting breaks up everyones day, making it more difficult for attendees to have long uninterrupted periods of deep, concentrated work.
But there wasn't anything to code yet, or if there was, that wasn't explained to him yet, so, ????
Morale: don't write code if there's no clear "what to build".
Some of the debate I'm seeing here is lacking synthesis of the tradeoffs. First, getting people to communicate is essential (a collective activity). Second, giving individuals time to work productively is essential. Some work is done best solo, some is done best collaboratively. The key is intelligently striking a balance.