Re:What I Learned from Working 32 Hours a Week
by ggurgone on Sunday January 06, 2019 @12:34PM
(#18839412)
> they are in roles where more time put in equals more work done
This is partially true if:
1) you only hire young folks 2) you don't care about long term health of your team
Based on this philosophy I could work 90h/week and get even more done i.e. there is always work to be done but IMHO this way of working is unhealthy and not sustainable.
Personally for me it takes more time than the average to recharge so having a shorter working week helps with recharging and do well next week and be productive. And by that I mean being equally productive to a "full time".
> if you aren't paying 100% attention, that doesn't cost money
I'd argue it can cost you money, in different ways.
Re:What I Learned from Working 32 Hours a Week
by guitarbill on Sunday January 06, 2019 @01:56PM
(#18839883)
I'm saying managers or clients aren't always technical, and for some of these non-technical roles, time is correlated to amount of work done, so they assume technical work is also like that.
Almost nobody can do more than 3 hours of heavy concentration/flow work regularly. Add another two or three hours for meetings, answering emails, triaging bugs, etc. and you get ~30h per week. When I'm in a position to do so, I tell my team that I'd rather have 3 hours of great work than 6 or 8 hours of mediocre work full of mistakes.
Still, it's an uphill battle culturally. And sometimes even developers don't like it, since they can't hide a lack of output behind hours in the office. I think this is a positive, because as a team lead you notice issues quicker, e.g. if someone is having a rough week. But it's also a good way to "unmask" people who e.g. embellished their skill level during the hiring process and maybe aren't a great fit for the role. That way, you can get them the training they need, or find them a different role.