Having it be the first thing in the morning seems to be the least efficient option possible, way worse than being interrupted in flow. This is the peak working time for most people, peak alert time for the majority of the population, and therefore the most productive time for many people, even many of those who are not prone to waking up early. Starting with something that's mostly useless to the developer and taking focus away from what really needs to get done that morning sometimes kills the entire morning. I'd rather be interrupted mid-flow and I'm certain I'm not alone considering the majority of the population actually is most alert in the morning (along with the other peaks of energy throughout the day). The optimal time for such a meeting would probably be either right before or after lunch, with lunch being variable and taken based on the workload of that day.
Comments
Having it be the first thing in the morning seems to be the least efficient option possible, way worse than being interrupted in flow. This is the peak working time for most people, peak alert time for the majority of the population, and therefore the most productive time for many people, even many of those who are not prone to waking up early. Starting with something that's mostly useless to the developer and taking focus away from what really needs to get done that morning sometimes kills the entire morning. I'd rather be interrupted mid-flow and I'm certain I'm not alone considering the majority of the population actually is most alert in the morning (along with the other peaks of energy throughout the day). The optimal time for such a meeting would probably be either right before or after lunch, with lunch being variable and taken based on the workload of that day.