3 ms·
"In my experience, the biggest pitfall is when developers try to force 100% asynchronous communication at all costs," In my experience, the biggest pitfall is
by k__ 7y ago
"In my experience, the biggest pitfall is when developers try to force 100% asynchronous communication at all costs,"
In my experience, the biggest pitfall is when non-developers try to force 100% synchronous communication at all costs.
I always had the experience that there is a struggle to get people to accept async work because everyone thinks it's normal to call everyone all the time.
- openthc 7y agoBalance. Chat on mattermost for all day noise, dm and open webconf for the Swarm on the problem, combined notes on ticket for historical.
- k__ 7y agoMost is also cultural fit. Some peole need three calls until they understand what I'm telling them. For others it's three slack messages a week and we are all good.
- t34543 7y agoI couldn’t agree with this more. My org is full of people who love meetings. On average it’s 30 hours of meetings per week, absolutely insane. I’ve been training people to not invite me so it’s down to 10, but still higher than I would like.
- k__ 7y agoThis. I don't think 100% async is the way, but I think it's easier to end up with too much sync than with too much async.