I like when you discussed the scenario of async communication to the person sitting right next to you. I use to think it was the weirdest thing, why can they just come up directly in person. But I realized how important is flow and deep work. Sending the message async is actually very considerate from that perspective.
![[WIP] Podcast](https://substackcdn.com/image/fetch/$s_!qo9l!,w_80,h_80,c_fill,f_webp,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb1f6d9a2-dfed-4d85-9f15-77259e2ab5b5_1280x1280.png)
![[WIP] Podcast](https://substackcdn.com/image/fetch/$s_!qo9l!,w_36,h_36,c_fill,f_webp,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb1f6d9a2-dfed-4d85-9f15-77259e2ab5b5_1280x1280.png)
I like when you discussed the scenario of async communication to the person sitting right next to you. I use to think it was the weirdest thing, why can they just come up directly in person. But I realized how important is flow and deep work. Sending the message async is actually very considerate from that perspective.
Great point! I didn't realize how important flow state was before switching into software engineering, myself.
And so many non tech people get this wrong and it’s killing productivity.
There’s a study that found it takes 23 mins to get back to what you were doing after an interruption.
So that 1min question your product person had… just cost 24mins of productivity