CSCareerQuestions

894 readers

1 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Follow the programming.dev site rules
Please only post questions here, not articles to avoid the discussion being about the article instead of the question

Related Communities

!programming@programming.dev - a general programming community
!no_stupid_questions@programming.dev - general question community
!ask_experienced_devs@programming.dev - for questions targeted towards experienced developers

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

ericjmorey@programming.dev

odium@programming.dev

Have you ever encountered a real asynchronous work culture? (lemmy.zip)

submitted 2 months ago by Blaze@lemmy.zip to c/cs_career_questions@programming.dev

4 comments fedilink hide all child comments

The most famous example is probably Gitlab (https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/)

Since their IPO the work environment seems to have deteriorated though (https://old.reddit.com/r/devops/comments/152o4bb/what_the_hell_is_going_on_at_gitlab/)

Curious to see if other people have any experience of real asynchronous work culture?

top 4 comments

sorted by: hot top controversial new old

[–] Semi_Hemi_Demigod@lemmy.world 1 points 2 months ago

The last job I had didn't have a fully asynchronous culture, but did treat December and August as asynchronous months because it let people have more flexibility with time off.

[–] agressivelyPassive@feddit.de 1 points 2 months ago (1 children)

Honestly, that sounds like a horrible idea.

Yes, excessive meetings suck, but there are so many problems that are 20 emails over a period of 4 days, or a 5min call.

[–] ericjmorey@programming.dev 1 points 2 months ago* (last edited 2 months ago) (1 children)

Often neither the 5 minute call nor the 20 emails are needed but used because no prioritization is being made for the time or work of others because there's not enough friction to force the prioritization. Not everything that is urgent is important and not everything that is important should interfere with urgent matters. The balance is difficult in any arrangement.

Also, you can send an email to schedule a call.

[–] agressivelyPassive@feddit.de 0 points 2 months ago

You're conflating things.

Urgency is not a factor, but brevity and mental load. Writing mails takes time and forces you to jump between issues/contexts. Even if you answer all mails in one go, you still need to switch contexts again and again. Add to that the inevitable misunderstanding in written communication and you end up with hours of work for simple questions.

Of course there are issues that can be resolved via mail/tickets just fine, but many can't. Forcing employees to choose a certain channel is not a good idea.

Also, you can send an email to schedule a call.

Why are companies going async? To go global. Now find a slot that works for Central/Western Europe and California. Good luck.