4 ms·
40 hour max work weeks enforced and 4 day work weeks. Shifts for people that need to monitor ops. Offices for everyone on staff that like to work in a quiet pl
by zitterbewegung 8y ago
40 hour max work weeks enforced and 4 day work weeks. Shifts for people that need to monitor ops.
Offices for everyone on staff that like to work in a quiet place and pubic areas for people who like to work in those places .
Also, the minimization of time spent in meetings .
- deleted 8y ago[deleted]
- nkingsy 8y agoWas funny seeing the BBC article on "Office Space" yesterday talk about the switch to open offices without mentioning the backlash. Was sure HN would be up in arms.
- protonimitate 8y ago> Also, the minimization of time spent in meetings I would argue that this should be "the minimization of unstructured/unguided/unclear meetings". Tbh I've seen a non-trivial number of instances where engineers have wasted their own time or someone else's by not participating in organizational meetings - either by doing redundant work or having an unclear image of priorities/blockers/help needed. Nobody want's to waste time in meetings, and most people who call meetings can't run them well. BUT having a well planned and executed meeting (30 mins tops) can save hours if not tens of hours of work time per week. I also believe that the "just let the devs do dev work and avoid meetings" mantra is border-line meme status and (in my opinion) stems from toxic anti-social behavior, rather than efficiency. However, I also believe that meeting time per week should have an upper-bound (something like 4-6 hours, including a 15-min daily standup) to better enforce efficiency, rather than throwing 1-hour meetings all over the place and hoping they don't use all the time.