News for hackers. Stuff that matters.
Re:Working asynchronously by k__ on Thursday October 24, 2019 @03:22PM (#21348246)
"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.

Re:Working asynchronously by t34543 on Thursday October 24, 2019 @07:52PM (#21350371)
I 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.
Re:Working asynchronously by k__ on Thursday October 24, 2019 @08:49PM (#21350726)
This.

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.

Re:Working asynchronously by openthc on Thursday October 24, 2019 @07:19PM (#21350176)
Balance. Chat on mattermost for all day noise, dm and open webconf for the Swarm on the problem, combined notes on ticket for historical.
Re:Working asynchronously by k__ on Thursday October 24, 2019 @08:48PM (#21350718)
Most 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.