I wanted to chime in here and mention the concept of "Email Apnea"¹. The idea is that we hold our breaths when anticipating an outcome. The term was coined in

I wanted to chime in here and mention the concept of "Email Apnea"¹. The idea is that we hold our breaths when anticipating an outcome. The term was coined in relation to email, but I believe that programmers probably have it even worse, because we basically spend our entire day in a a loop where we, try something, anticipate the results try again, repeat... I personally find myself doing it. I guess the best analogy for it is that we "wait with bated breath" to see the results of our last command or compilation. I think it's a problem inherent in all disembodied work. We are supposed to move the body and the mind as a unit, instead, we are increasingly making ourselves into brains in a jar, and I think our breathing patterns reflect it. 1: https://www.msn.com/en-us/health/medical/email-apnea-is-a-real-thing-here-s-how-to-stop-holding-your-breath-while-working-and-feel-less-stressed/ar-AALmCqX https://www.msn.com/en-us/health/medical/email-apnea-is-a-re...