27

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?

you are viewing a single comment's thread
view the rest of the comments
[-] agressivelyPassive@feddit.de 3 points 6 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.

[-] ericjmorey@programming.dev 3 points 6 months ago

Now find a slot that works for Central/Western Europe and California.

I was scheduling calls from EST with people on AEDT 20 years ago. Companies having a global presence isn't a new issue. Everything is a trade off and sometimes the cost of asynchronous work communication is beneficial.

this post was submitted on 12 Jun 2024
27 points (93.5% liked)

CSCareerQuestions

987 readers
1 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Related Communities

Credits

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

founded 2 years ago
MODERATORS