4 ms·
When I played EVE Online long ago, we had 1/3rd of people from east coast, 1/6th from west coast, 1/3rd from Europe and the rest from Australia, we came up with
by lstodd 6y ago
When I played EVE Online long ago, we had 1/3rd of people from east coast, 1/6th from west coast, 1/3rd from Europe and the rest from Australia, we came up with pretty efficient framework.
It only takes accepting that the work has to be mostly asynchronous, then build processes around that.
If deadlines loom and you have to talk urgently, that means the processes were inadequate - that is all.
All those "hybrid/flexible" schemes are doomed to fail. Remote work isn't office work at all, it's quite different. This is also what drives management nuts in my opinion - they feel that stuff has to be changed significantly and they don't know how, or if they are now in fact redundant.
- eigenket 6y agoI think this comment is coming from a very different place to my experience. Academic work is much less predictable than the sort of work you seem to be talking about. Like we're doing maths that no one in the world has done before, and which is objectively kinda hard. When we notice a mistake a few days before a big conference deadline (which is actually what happened around the end of last year) its hard to imagine any process could be adequate to stop that happening. Mistakes get found even in peer reviewed papers all the time, admittedly usually innocuous ones. You seem to be suggesting processes for vetting our internal stuff which are more stringent than actual peer review.