4 ms·
This article seems to be tearing down a straw-man. I don't see people arguing that you must be in a "flow" state 100% of the time, or suggesting that all time
by mindcrime 10y ago
This article seems to be tearing down a straw-man. I don't see people arguing that you must be in a "flow" state 100% of the time, or suggesting that all time not spent in "flow" is useless. The argument, as I've seen it, is just that when you have the opportunity to get into a flow state, it's a Good Thing, and that one should try minimize distractions (cough open plan offices cough) that are likely to keep on from being able to achieve "flow" or sustain in for useful periods of time.
- leighbryant 10y agoIt's the idolization of the flow state that I take issue with. Flow, as the article states, has advantages. But the tech industry puts it on a pedestal, to the detriment of teams and active collaboration. It discourages discussion and communication for fear of disrupting a precious, fragile work-state; it makes those who don't get into that zone feel lesser-than and like they are failures; and it makes those that do get into that zone chase it with single-minded zeal and drive themselves to exhaustion in the process. To paraphrase another commenter from a different channel, the "fetishization of overwork" that comes with the constant, heady pursuit of flow is what I push back against. Flow itself is fine. The culture surrounding I find very problematic.