interesting idea in theory. won't work in practice. the 4h has to be shared. everyone on the team has to be in menstrual synchrony, so to speak. this type of w

interesting idea in theory. won't work in practice. the 4h has to be shared. everyone on the team has to be in menstrual synchrony, so to speak. this type of work requires one to get "in the zone", or achieve the "flow" state. everyone has different biorhythms and won't even maintain the same time schedule on a daily basis or even weekly basis. in an 8hr day you might get 3-4hr of good performance. yes you can do better, but not on a sustained basis. yes more hours per day will give you more but after 8 it really starts to become a diminishing returns thing. if you tell people to only do 4hr of work, the output is going to be 1-2 hr of efficient work. you are basically claiming it's a team sport but want to apply a principle that would only work for you personally. now if you can hire only people "like you" then you're golden. or, if you can pay (say) 2-5x market, fire quickly, compel people to have a very specific training-like schedule with execute-or-GTFO practices, have a high demand but high performance environment, only hire high experienced devs, then you might have something. it's not generalizable to the extent that it is usable advice or recommendation. lastly does your 4h of work include communication and coordination functions? if so, it's reduced to 2h of work.