Programmer interrupted: The cost of interruption and context switching (2022)
If I know I am going to have my day broken into sub 1hr chunks thanks to meetings and such, I pretty much write off the day entirely. It takes time to get into the flow state, some studies cite over 20 minutes, and once you are in it you want to stay in it for like four hours. No emails to follow up with, no slack, no zooms, no one tapping your shoulder, no conversations about the weekend distracting you on the periphery, just you and your task at hand.<p>It&#x27;s pretty ironic, because this is how a lot of people study in the library at college,show up and stay all night grinding in the flow state with your phone shut off. Yet when you graduate to the work place, you seldom have the opportunity to work like how you&#x27;ve been training to work for all your advanced schooling ever again.<p>With respect to the article and maintaining context while coding for different projects, I find having a tmux session for each individual project super helpful.