This does not strike me as surprising or problematic, as the choice of headline would suggest. They specify 4 hours of "focused" work. That seems a perfectly r

This does not strike me as surprising or problematic, as the choice of headline would suggest. They specify 4 hours of "focused" work. That seems a perfectly reasonable amount of time to remain in the flow state on an average workday. Email/Slack, meetings, and administrative tasks can easily eat up the rest of the day. Expecting engineers to churn out 8 hours of raw code/infra/documentation every day is not sustainable or even desirable in most cases.