In fact, the last company I worked at had hired way too young, and they had a bunch of kids who thought that being in your office writing code was somehow "Bad" because you were "siloed away". They liked to hang out all together at one big table, and chat away all day long with their laptops out.
In the time I was there, I don't think they ever realized they were getting nothing done. (I was curious as to whether they were onto something or not, so I tracked the number of stories and features they committed vs. me and my officemate who at 26 was the "old man" of the bunch, though still much younger than me he was old enough to know what flow was.)
Result: the two of us were about 4 times more productive than the 5 of them.
One of those five, though, was the "director of engineering" (20 years old) and was constantly chastising us for spending too much time in our offices.
When it became clear that this was going to affect my evaluation, I chose to exit that company. (They folded about a year later, never having accomplished the short term goal they were working on while I was there.)
But maybe I'm wrong. Maybe some people are more productive in groups of 2-3. That's fine. Set up offices for them to work that way.
Just let me have some damn peace and quiet so I can get work done! (and I never seem to have a problem hooking up with other engineers to talk about architecture or what have you to keep us coordinated, though often this is via email or chat... which is much less interrupting than a tap on the shoulder.)
-----------
On further thought-- maybe designers and people whose job is to sling HTML or javascript don't need to have "Flow". Maybe the jobs for these people are light enough that there is no context switching cost or the cost is low. That's not the case for my work or my career. There's often a very large amount of stuff I need to track in my head... because I'm generally solving hard problems on the back end, rather than making UIs or web pages.