So if you value flow, if you think that getting away from noise and distraction is valuable and lets you write good code, that inevitably means a totalizing rem

So if you value flow, if you think that getting away from noise and distraction is valuable and lets you write good code, that inevitably means a totalizing removal of oneself from the customer? Perhaps the author needs to discover nuance. There is a time for coding and a time for working with your team and with customers. Unfortunately he posits two positions: "always" or "never" and every approach must fit into one of those two. He has a brief flirtation with nuance, comparing a couple of weeks to a couple of days, but quickly abandons it by declaring an inevitable outcome. Yes we do "win when everyone comes together, with the customer at the center", but I don't see why one bad extreme means we need to throw out every valuable learning about flow. TL;DR Flow isn't bad, hiding away is. Don't confuse the two. (And put away the hammer.)