We kind of have the opposite problem on my team... all the devs tend to work mostly alone (98+% of the time). Most of the dev communication is with the product owner and the product engineers (non-devs).
We talk about doing pair programming or something in the next release, then we all go back to our respective stacks of work and don’t feel like we have the time to collaborate on anything, unless it’s a question for someone who knows a part of the codebase better.
If the results in this study generalize, neither constant collaboration nor constant isolation are good. You want people to be able to crib ideas from you in a professional setting. You also want them to have enough time to think up their own ideas.
I know you didn't ask for advice, but perhaps code-review and design-review is actually all your team needs? i.e. instead of the constant collaboration of pair programming, you work on slightly lighter weight interaction by having pairs of people work on closely related projects code-reviewing each other and having times where they bounce ideas off each other, but who ultimately work alone till they produce something the other can see. A half-day boundary of interaction (non-formalized of course) may be sufficient to allow for the degree of collaboration to be fruitful.
We talk about doing pair programming or something in the next release, then we all go back to our respective stacks of work and don’t feel like we have the time to collaborate on anything, unless it’s a question for someone who knows a part of the codebase better.